Bubble.io · Glossary
Forty Bubble.io terms explained in plain language, with the ones that matter most when hiring and questions to ask using them.
Last updated: October 2026. Written by Athar Ahmad, Certified Bubble.io Developer and Tech Architect, Simple Automation Solutions.
Quick answer
This glossary explains 40 Bubble.io terms in plain language, including data types, fields, relationships, option sets, privacy rules, roles, workflows, backend workflows, recurring events, repeating groups, custom states, searches and constraints, plugins, the API connector, workload units, development and live versions and the native mobile builder. The terms that matter most when hiring are privacy rules, data types, development and live versions, backend workflows, workload units and searches.
Key takeaways
- Privacy rules and roles decide who can see what; ask how they are tested.
- Data types and relationships are the foundation of the app.
- Development and live versions are the safety net for changes.
- Workload units and efficient searches drive performance and cost.
- Option sets are not protected by privacy rules.
In this guide
This glossary explains forty terms you will meet when hiring a Bubble.io developer or working with a Bubble app, in plain language. Bubble’s features and names change over time, so check its documentation for the latest details.
The 40 terms
| Term | Plain-English meaning |
|---|---|
| App editor | The visual workspace where you design pages, define data and build workflows. |
| Development version | The copy of the app where building and testing happen, separate from the live version. |
| Live version | The version of the app real users use. |
| Deploy | Publishing changes from the development version to the live version. |
| Data type | A category of information the app stores, such as Client or Invoice. |
| Field | A single piece of information on a data type, such as an email address. |
| Thing | A single record of a data type, such as one client. |
| Relationship | A link between data types, such as an Invoice belonging to a Client. |
| List | A group of records or values, for example all documents for a matter. |
| Option set | A fixed list of choices shared across the app, such as statuses or categories. Not protected by privacy rules, so not for sensitive data. |
| User | The built-in data type for people who log in. |
| Current User | The person using the app right now, used in rules and conditions. |
| Privacy rules | Conditions on each data type that decide which users can see which data, enforced by the platform. |
| Role | A category of user with defined permissions, such as client, staff or admin, usually implemented through data and privacy rules. |
| Workflow | A series of actions triggered by an event, such as a button click or a form submission. |
| Event | The trigger that starts a workflow. |
| Action | One step within a workflow, such as creating a record or sending an email. |
| Condition | A rule that decides whether something happens, such as showing an element only to admins. |
| Backend workflow | A workflow that runs on the server rather than in the user’s browser, often used for scheduled or background tasks. |
| API workflow | A backend workflow that can also be triggered by an outside system through an interface. |
| Recurring event | A workflow that runs on a schedule, such as sending reminders daily. |
| Scheduled workflow | A workflow set to run at a specific future time. |
| Page | A screen in the app, built from elements. |
| Element | A building block on a page, such as a button, input or table. |
| Reusable element | A component built once and used on many pages. |
| Popup | A box that appears over a page to show content or collect input. |
| Repeating group | An element that shows a list of records, such as a list of documents. |
| Custom state | A temporary value stored on an element or page while someone is using it. |
| Dynamic expression | A value calculated from data, such as a client’s name or a count of open tasks. |
| Search | A query that finds records, with constraints that narrow the results. |
| Constraint | A condition added to a search so it returns only matching records, which keeps the app efficient. |
| Plugin | An add-on that gives the app extra abilities, such as connecting to a service. |
| API connector | A tool for defining requests to outside services so the app can talk to them. |
| Integration | A working connection between the app and another service. |
| Workload units | Bubble’s usage-based measure of the work an app does, which influences hosting charges. |
| Responsive design | Layouts that adapt to different screen sizes. |
| Custom domain | Your own web address for the app, instead of a default one. |
| Debugger | A tool for stepping through the app to see what is happening and why. |
| Collaborator | Another person given access to edit the app. |
| Native mobile builder | Bubble’s tool for building apps for the App Store and Google Play, which has been evolving through beta. |
Which terms matter most when hiring a developer?
- Privacy rules and roles: they decide who can see what. Ask how they are designed and tested. See our security guide.
- Data types and relationships: the foundation of the app. See database design mistakes.
- Development and live versions: the safety net for changes.
- Backend workflows: where scheduled and background logic lives.
- Workload units and searches: where performance and cost are won or lost. See workload units.
- Option sets: convenient but not for sensitive data.
Questions to ask using these terms
- How will you set privacy rules on each data type, and how will you test them?
- How will the data types and relationships be structured?
- How do you work between the development and live versions?
- How will you keep searches efficient and workload units low?
- Which parts need backend workflows or scheduled tasks?
- Which plugins and integrations will be used, and who owns the keys?
For a broader list of terms, see our general glossary for founders. Builds at Simple Automation Solutions start at $3,500, and a $345 Discovery Sprint, credited toward the build, turns your idea into a plan using these concepts.
Frequently asked questions
What is a data type in Bubble?
A category of information the app stores, such as Client or Invoice, with its own fields and relationships.
What are privacy rules in Bubble?
Conditions on each data type that decide which users can see which data, enforced by the platform.
What is a backend workflow?
A workflow that runs on the server rather than in the user’s browser, often for scheduled or background tasks.
What are workload units?
Bubble’s usage-based measure of the work an app does, which influences hosting charges.
What is the difference between development and live versions?
The development version is where building and testing happen. The live version is what real users use. Changes are deployed from one to the other.
Want these terms applied to your project?
Email us your idea. We will explain how it would be built, in plain language.
Athar Ahmad, Certified Bubble.io Developer and Tech Architect, Simple Automation Solutions
About Simple Automation Solutions (SA Solutions)
Simple Automation Solutions is a Bubble.io development studio led by Athar Ahmad, a Certified Bubble.io Developer and Tech Architect. It builds web and mobile apps, client portals and SaaS products for founder-led businesses such as law firms, accounting firms, boutique agencies and consultants. Services include a free 30-minute Idea Audit, a $345 Discovery Sprint (a Product Requirements Document delivered within 24 hours, credited toward the build) and builds starting at $3,500. Website: sasolutionspk.com.
