Hi everyone,
I am building my first app with Bubble, I am a designer with frontend skills but low knowledge of backend. I would like to ask your advice on how to properly set up the app re getting-data-from and writing-data-to the database.
Mainly, my idea would be to create backend workflows with API calls for ALL the queries that I need to do, even when this might return few data points only.
The reasons are:
performance in case the app flies
scalability in case the app flies
easier management (all calls are in the same place)
ability to reuse these calls from a mobile app
To make an example, I am thinking about having calls like “getProducts” or “getModules” that will retrieve a list of items from my own database/Bubble app - I see in the docs backend workflows are always mentioned as calls to external API endpoints.
What is your opinion about this approach? How are you setting up your app? Do I need any tools to do this (I think API Connector is required, right?) What else should I consider (for sure I am missing something?)
Bubble’s built-in data fetching (Do a search for…) is already optimized for Bubble’s own database.
Adding backend workflows for every single query can actually add extra overhead (API calls, more latency, more complexity).
The general rule is:
Use direct data sources (Do a search for) when building pages inside Bubble.
Use backend workflows when you actually need logic behind the scenes (e.g. heavy processing, manipulating large lists, scheduled jobs, secure data flows).
2. Performance & scalability
Bubble’s database queries scale fine up to quite large apps. You can use constraints and privacy rules to keep data fetching efficient.
API-based calls add an extra HTTP layer → more network hops, slower.
If you expect millions of records, then eventually you’ll need external databases or APIs. But Bubble’s built-in DB is usually good for MVP and beyond.
3. Centralized management
Yes, backend workflows give you a nice “all in one place” feel, but you lose the simplicity of Bubble’s native expressions.
A good compromise:
Keep “special cases” (complicated business logic, reusable transformations) in backend workflows.
Keep standard queries as native searches.
4. Mobile app reuse
If you’re planning a mobile app later, you don’t need to pre-wrap all queries in backend workflows.
Bubble auto-generates Data API endpoints (you just need to enable them in Settings → API).
These endpoints are RESTful and can be used directly in a mobile app.
Backend workflows are great if you want custom APIs beyond Bubble’s default CRUD endpoints.
5. Tools required?
API Connector: only if you want to call external APIs.
For your own Bubble DB: you don’t need API Connector — just enable the Data API or use Bubble’s native search inside your app.
Backend workflows are built into Bubble (you enable them in Settings → API → check “Enable workflow API and backend workflows”).
Suggested setup
In-app queries: use Bubble’s Do a search for… with constraints + privacy rules.
Heavy jobs / sensitive logic: put them in backend workflows.
For mobile apps: expose Data API or define custom API endpoints (backend workflows).
For performance: always design searches with constraints, avoid :filtered where possible, and limit results when you don’t need full lists.
My advice:
Start simple (direct searches), add backend workflows only when you have a real reason. Don’t over-engineer too early — Bubble’s “native way” is already optimized.
No offence but you should at least provide some of your own thoughts instead of just copy pasting AI responses wholesale.
To OP
I cannot speak for the section on mobile because I’m not bothering with it until I can write my own plugins for mobile. Otherwise, the responses are correct. Don’t need to over engineer anything when it comes to working within Bubble’s stack.
Correct. Fortunately, you have control to expose it as an endpoint for external requests or just for use internally within your app.
Take some time to read through the docs and official tutorial videos to get a better understanding of how Bubble works in regard to data management.
A quick primer on app management, scaling, security and performance in Bubble is to understand:
how to set appropriate privacy rules
properly set up workflows and conditions
how to schema and structure your Bubble database
when and how you can use Reuseable Elements for app management
Bubble does a good job when scaling, but it requires putting a lot of attention to when and what data you are requesting at different points of the user journey. That said Bubble can pretty much scale indefinitely since you can choose to go enterprise or easily integrate external stacks (my preferred method).
Disregard the whole Bubble is a bad frontend noise you hear in the forums. It’s not the best but from experience I will confidently say that it depends on what kind of frontend you need Bubble to be. Another perk is if you want to keep room for migration to native in the future, stacking your own solutions will make the migration easier when it happens.
1. Backend workflows for all queries?