Hey everyone,
I’m working on a dashboard-style app in Bubble that includes multiple repeating groups on a single page — some horizontal, some vertical, showing real-time data, charts, and user-specific content.
It’s coming together nicely, but I’ve noticed the page performance starts to drop as the data grows — especially on mobile.
Just wondering, how do you all handle performance when dealing with:
- Multiple repeating groups on one page
- Conditional formatting inside cells
- Real-time updates or auto-refreshing data
- Mobile responsiveness without killing speed
I’ve tried lazy loading and simplifying some conditions, but I’d love to hear what strategies or best practices others are using — especially in production apps.
Thanks in advance!
One strategy that might give you noticeable results is using satellite datatypes. You have a nice guide about them by @petter here.
They’ll allow you to show info on dashboards without downloading heavy records to your users’ browser. You’ll need to do some DB reestructuration, but it’s bearable.
1 Like
you can check out my paid plugin called Data Jedi that when used to power a Hybrid data structuring approach improves performance of data loading by between 30-50% when compared to legacy approaches like using satellite data types. It also reduces the WU costs of fetching data by 95% compared to legacy approach of satellite data types and reduces WU costs of creating the data (when done in one more than just one item at a time - this savings is compounded as the number of things created at once increases so, it can reduce the WU costs by 99%+)
There are a ton of other features that improve performance and help improve the speed at which the pages load initially and how navigating from one section of a dashboard or SPA, one of which is the Paginator element, another is the Local Storage functions.
On the road map is an element that is a ‘templater’, which will allow users to create templates for things ranging from meta data (page title or description for use in SEO) to Contracts or Quotations that can then be sent through to a PDF builder (when this is added it will create the pdf).
The Hybrid data structuring approach uses API objects which work the same exact way as a custom data type would, so you can have real time updates as data changes in the DB reflected instantly in the RG and even have backend database trigger changes based on the fields of the api object and not just the fields of the custom data type.
It currently has as well a searchbox element that simplifies the development of searching data types by finding matched suggested values while typing. This also helps with performance, speeds up development, and adds some great filtering functionality for dashboards.
This is how I am managing and improving performance on pages, dashboard pages and SPAs.
