Input forms are how you collect information from your users. They range from simple text fields and toggles to more complex controls like date pickers, dropdowns, and selectable lists.
Bubble includes a range of built-in input types for common needs, letting you build everything from a quick signup form to a detailed multi-step questionnaire. Each input type is designed to feel native to the platform, matching the interactions users expect.
Input
Input elements accept a single line of plain text, and you can choose its content format from a wide range of options. Inputs in native mobile apps don't support text formatting such as bold, italics, or bullet points, so any text they return is plain text. The Field type returned in the list below specifies what kind of database field format the input returns.
Because of the predictive text functionality on Android devices, some content formats involving masks have a slightly different UX. This applies to US phone, Percentage, Currency, Date, Euro date, and Text (numbers only).
On Android devices, the input lets users type anything and validates the content against the mask only after the user stops typing.
This doesn't affect the final data generated by the input.
Text
The input accepts any text value.
Field type returned: text
An input with the Text content format.
The input only accepts text values that are formatted like an email address.
Field type returned: text
An input with the Email content format.
Password
The input accepts any kind of text value, but the characters typed are replaced by asterisks.
Field type returned: text
An input with the Password content format hides the characters as the user types.
Integer
The input only accepts whole numbers. Use this when you need to collect numerical values that can later be used for calculations (as opposed to numbers saved as text). You can specify a dynamic minimum and maximum value when this option is selected.
Field type returned: number
An input with the Integer content format.
Decimal
The input accepts any whole number or decimal number. You can specify a minimum and maximum value, as well as the number of decimals to include. You can also set the input to automatically include thousands separators as the user types. This option is only visual and doesn't affect the final value.
Field type returned: number
An input with the Decimal content format.
Address
A geographic address. With this option, the input automatically validates the address with Google Maps. Note that the input doesn't search for valid addresses as the user types, so the user has to provide an already valid address (for example, by copying and pasting it from Google Maps).
Field type returned: address
An input with the Address content format.
US phone
This input accepts correctly formatted US phone numbers. The value is saved as text.
An input with the US phone content format.
Field type returned: text
Percentage
This input formats the user's input as a percentage and accepts input such as 20%. Bubble automatically saves it as the numerical equivalent of the percentage. For example, 20% is saved as the number 0.2, and 150% is saved as 1.5.
An input with the Percentage content format.
Field type returned: number
Currency
The input accepts any whole number or decimal number and automatically formats the input in the chosen currency, such as $20. You can specify a minimum and maximum value, as well as the number of decimals to include. You can also set the input to automatically include thousands separators as the user types. The currency and thousands separators options are only visual and don't affect the final value.
An input with the Currency content format.
Field type returned: number
Date
The input accepts any date, but doesn't include time. It automatically formats the input's value as mm/dd/yyyy while the user types, guiding the user to provide the date in the right way. You can specify a time zone for the input, and Bubble automatically calculates any offset from the user's current time zone. If no time zone is provided, the user's current time zone is used. Dates are saved at 12 AM (00:00) on the given date.
An input with the Date content format, using the mm/dd/yyyy order.
Field type returned: date
Euro date
The input accepts any date, but doesn't include time. It automatically formats the input's value as dd/mm/yyyy while the user types, guiding the user to provide the date in the right way. You can specify a time zone for the input, and Bubble automatically calculates any offset from the user's current time zone. If no time zone is provided, the user's current time zone is used. Dates are saved at 12 AM (00:00) on the given date. The difference between this content format and the Date format is purely visual.
An input with the Euro date content format, using the dd/mm/yyyy order.
Field type returned: date
Text (numbers only)
This input only accepts whole numbers, and the result is saved as text. This is useful when you want to save numerical values that need to remain exactly as the user typed them (without losing leading zeros, for example) and won't be used for any type of calculation, such as international phone numbers, zip codes, and order numbers.
An input with the Text (numbers only) content format looks like a number input, but saves the value as text.
Field type returned: text
Storing numbers as text versus storing them as numbers
Storing numbers as text versus storing them as numbers
What is the difference between the two?
The Bubble database offers two different field types that can both be used to save numerical values: text and number.
There are a few scenarios where it makes sense to save a number as a text string:
When you need to include leading zeros
In an integer (or number), a leading zero represents no value and is disregarded when saved to the database. After all, 045 and 45 are the same thing from a mathematical point of view, and the zero only adds confusion and increases the total size of the database.
Sometimes leading zeros are necessary. For example, a phone number or zip code might start with a zero, and it must be stored as text to preserve the complete value.
When you need to pass the data as text
Sometimes when you communicate with an external system through an API, that system may expect a numerical value to be passed as text. In that case, it can be useful to store it as text in the database to avoid having to convert it later.
When to use what
Text should be used when you're working with numerical values that will remain static and won't be included in any kind of calculation. For example:
Phone numbers
Zip codes
Postal codes
Product and part numbers
Numbers should be used when you're working with values that may need to be calculated or aggregated, such as:
Year of birth
Age
Counts and totals (such as the number of items in a cart and the cart's total value)
Financial numbers
Enumerated values, such as the values used to represent the days of the week (for example, Sunday = 0, Monday = 1, and so on)
Multiline input
As the name suggests, the Multiline input element accepts multiple lines of text. Like the regular input, this element supports plain text only and doesn't provide any custom formatting.
A multiline input grows to show several lines and paragraphs of text.
Use the Multiline input element when you need the user to be able to supply multiple lines of text but you don't want them to be able to add formatting such as bold, italics, and headers.
Field type returned: text
Date/TimePicker
The Date/TimePicker is a native mobile element created specifically for the native mobile app editor, offering an alternative to the date/time picker used in the web app editor.
It automatically adapts to the device's system, displaying the iOS picker on Apple devices and the Android picker on Android devices. This happens by default, with no additional configuration needed.
The Date/TimePicker uses the device's native component, so it won't render in web preview. Use simulated device or a dev build to test any flows that involve the Date/TimePicker.
Article: Previewing a mobile app
Appearance
The Date/TimePicker's properties control two key parts:
The element placed in the view
The native date/time picker, which appears when the user taps the element
Element properties
Picker style: Choose between:
Label/Icon: Show both a label and a customizable icon.
Label: Show just a label.
Icon placement: Choose to display the icon to the left (leading) or right (trailing) of the label.
Icon size: Set the size of the icon in pixels.
Icon color: Set the color of the icon.
Native date/time picker properties
Input type:
Date: Displays the date picker only. The value is stored in the database as the selected date plus the current time.
Time: Displays the time picker only. The value is stored in the database as the current date plus the selected time.
To combine the date from one picker with the time from another picker, you can use the
change time tooperator.
Accent color:
Color picker: Sets the color of a few properties in the calendar picker.
Minimum/Maximum date: Sets the minimum and maximum date and time that can be picked in the date/time picker.
Selectable lists
A selectable list functions as an input element that lets users select one or multiple options from a list. It's particularly useful for building filters, segmented controls, and selection forms without requiring additional custom states or workflows.
Selectable lists allow users to select one or multiple options from a list.
It can function in single-select or multi-select mode, with additional customization options for selection limits and workflow integration. Below are the key behaviors of the selectable list.
Single-select and multi-select behavior
Selectable lists can be set to single-select or multi-select mode, depending on how you want users to interact with them.
Single-select behavior
In single-select mode, only one option can be active at a time. Selecting a new item automatically replaces the previous selection, similar to how radio buttons work.
Users can also clear the current selection by tapping the selected item again, returning the list to an unselected state. This makes it easy for users to change their mind or start over without needing a separate reset action.
Multi-select behavior
In multi-select mode, users can choose more than one option from the list.
By default, there's no cap on how many items can be selected. If you want to limit the selection, you can set a maximum number of choices. Once the user reaches that limit, the remaining options are automatically disabled, and the user has to deselect an item before selecting a new one.
Validation and required lists
Selectable lists can be marked as required, similar to how you'd mark an input field as required. This helps make sure the user makes a valid selection before their data is saved.
The way validation appears follows the same pattern as required inputs:
Conditional styling for missing selections activates when the values are being saved. For example, if the user tries to submit a form without making a selection, the list can visibly indicate that a selection is missing, such as by highlighting a border or showing an error message.
The required styling clears automatically once the selection meets the requirement. In single-select mode, this happens as soon as an item is selected. In multi-select mode with a range restriction, the styling clears once the required number of items has been selected.
Performance considerations
The selectable list loads all items immediately, meaning it doesn't use lazy loading or virtualization like the vertical list.
Large data sets may impact performance, so it's a good idea to limit the number of options when possible.
This element is not a replacement for vertical lists and shouldn't be used for extensive lists of items.
Formatting selected items
The selectable list element has is selected and isn't selected data sources that you can use in conditionals to apply formatting to selected items.
This conditional adds a solid 1px border to an item when This SelectableListItem is selected.
The conditional must be set on the SelectableListItem pseudo child element, not on the selectable list element itself.
Workflows and actions
Workflows can be triggered when a user interacts with a list item. When adding a workflow from the list item property editor, the "When element is clicked" workflow event is automatically pre-filled.
The following actions are available for selectable lists:
Set selectable list value: Set a selected value for the selectable list (single item or list, depending on the selection type).
Select all: Selects all the available entries in the list.
Unselect all: Deselects all selected entries.
Display list: Set a list of entries for the selectable list, formatted as a list.
Clear list: Removes all entries from the list.
Scroll to entry: Scrolls the list to a specific entry.
Properties
The following properties are available on selectable lists:
's list of items (if multi)
's selected item (if single)
's list of selected items (if multi)
's list of unselected items (if multi)
's minimum number of selections (if range is selected)
's maximum number of selections (if range is selected)
's number of allowed selections (if exact is selected)
Width
Height
isn't valid
is disabled
Conditional properties
The following conditional properties are available on selectable lists:
Minimum number of selections (
number): The minimum number of selectable entries, as specified in the minimum number of selections propertyMaximum number of selections (
number): The maximum number of selectable entries, as specified in the maximum number of selections propertyNumber of selections (
number): The current number of selected entries
Checkbox
The Checkbox element provides an intuitive way to manage selection states without needing complex workflows or custom states.
Here are two common use cases for the Checkbox element:
Filtering to-dos
The Checkbox element can be used to filter lists, such as a list of to-do items. Instead of manually creating icons, workflows, and custom states to manage selections, you can add the Checkbox element directly to each list item. The checkbox works similarly to a button, allowing for customization of icons, labels, sizes, and colors.
It also includes built-in conditionals for the checked and unchecked states, making it simple to toggle between states by tapping. The current value of the checkbox is easily readable, so you can trigger actions based on whether it's selected or not.
Managing task status
Another common use case for the Checkbox element is to visually indicate task completion. For instance, when a task is marked as done, the checkbox appears checked, and when a task isn't done, it appears unchecked. You can modify the default state of the checkbox through conditionals. For example, if a task is marked as complete in the database, the checkbox automatically reflects that state by appearing checked.
Key features
Customizable appearance: Adjust icons, labels, colors, and sizes.
Default checked/unchecked states: Built-in toggling functionality.
Conditional behavior: Reflect the current state based on conditions (for example, task completion).














