This article explains the form field field types and components available on Quickbase mobile, as well as any differences between the desktop and mobile experiences. It also lists upcoming features planned for mobile forms.
In this article
Field types
Field type | Viewing records | Adding/Editing records |
Text | Same behavior as desktop | Same behavior as desktop |
Text - multi-line | Same behavior as desktop | Same behavior as desktop |
Text - multiple-choice | Same behavior as desktop |
Multiple choice options are presented in a modal. Users can:
|
Multi-select - Text | Same behavior as desktop |
Multi-select options are presented in a modal. Users can:
|
Rich text | Same behavior as desktop | Same behavior as desktop |
Numeric | Same behavior as desktop | Same behavior as desktop |
Numeric - currency | Same behavior as desktop | Same behavior as desktop |
Numeric - percent | Same behavior as desktop | Same behavior as desktop |
Numeric - rating | Same behavior as desktop |
If the field is configured with input type User input, then the behavior of the field will be the same as desktop.
|
Date | Same behavior as desktop | A date picker will be presented in a modal. Once the user makes a date selection, they need to confirm their choice by tapping OK. |
Date/Time | Same behavior as desktop | Date and time pickers will be presented in a modal. Once the user makes a date and time selection they need to confirm their choice by tapping OK. |
Time of day | Same behavior as desktop | A time picker will be presented in a modal. Once the user makes a date selection they need to confirm their choice by tapping OK. |
Duration | Same behavior as desktop | Same behavior as desktop |
Checkbox | Same behavior as desktop | Same behavior as desktop |
Address | When users tap on an address link:
|
For both Address fields and Latitude/Longitude fields, mobile users can either:
If there is an entered address value, the user can go to their maps app by pressing the Open button (displayed below the fields and map):
|
Phone number | When the user taps on a phone number they will automatically be navigated to the Phone app on their device with the phone number being automatically populated. | Same behavior as desktop |
Email address | Same behavior as desktop | Same behavior as desktop |
User | Same behavior as desktop |
User options are presented in a modal. Users can:
Limitation: User fields on mobile don’t support the functionality to search the realm or invite new users. You can select only from the list of users with access to the app. |
List - user | Same behavior as desktop |
List-user options are presented in a modal. Users can:
Limitation: List-user fields on mobile don’t support the functionality to search the realm or invite new users. You can select only from the list of users with access to the app. |
File attachment |
When a user taps on an attached file the app will open a preview of the file. The following file types can be previewed directly in the app:
For all file types the user will be able to download/share the file from the preview screen, no matter if the file can be previewed or not. Limitation: Revision history and lock/unlock file flows are not yet supported on the mobile version of forms. |
Users can choose between:
Limitations:
|
URL & URL formula |
Same behavior as desktop Note: On iOS, all Quickbase pages embedded on a form or dashboard require end users' permission to view. This includes Code pages and the File Manager plugin. Users only need to give permission once (unless the app is reinstalled), but must select the View button each time. |
Same behavior as desktop |
Report link | Same behavior as desktop | Same behavior as desktop |
Reference | Same behavior as desktop |
Options are presented in a modal. Users can:
|
Predecessor | Same behavior as desktop |
Predecessor options are presented in a modal. Users can:
|
Work date | Same behavior as desktop | A date picker will be presented in a modal. Once the user makes a date selection they need to confirm their choice by tapping OK. |
All standard Quickbase form and field limits apply to the mobile version of forms, as well. Learn more about limits in Quickbase.
Form components
Pinned section
The pinned section on mobile remains at the top of the form, below the form tabs, and is visible across all tabs. On mobile, these sections are always collapsible by default to optimize navigation on smaller screens. This behavior ensures a streamlined user experience and cannot be modified by the builder.
Embedded reports
Embedded reports on mobile function similarly to those on desktop forms, but with some limitations: users cannot use grid edit, filter reports, or export to CSV.
Depending on permissions, mobile users can view reports, search, add new records, edit or view individual records, and delete records.
Sub-forms are not supported on mobile, and actions like adding, editing, or viewing a record navigate the user to a new page.
Rich text
Just like desktop forms, builders can add rich-text components for non-editable text on mobile forms. The mobile version of the form honors all component customizations. Learn more about rich text components in forms.
Sub-forms
Not supported on mobile. Instead of presenting a sub-form, the mobile experience will directly navigate the user to the full form.
Form spacing
Not supported on mobile. On desktop forms end users can control the display density of a form with these spacing options: Relaxed, Normal, or Condensed. The mobile version of forms supports only the Normal density.
Upcoming features
-
Barcode scanning
-
Next and previous record navigation
-
Timezone helper
-
The following parameters for setting navigation paths after form save:
aftersaveview=1
aftersaveconfirm=1
aftersaveurl=
aftersavenew=1