Are you creating all the functionality for the different ‘components’ on that single page?
I’m sure you have groups that are visible or not at different times depending on how the user is navigating and inside of those groups there are specific feature sets…my question is whether or not you are creating all the elements and the workflows for each group on that same single page in your editor.
If you are, that is the reason for the slow editor.
To get around this, instead of creating each feature set on the same page, I create the individual feature sets in a reusable element and then I place the reusable elements into groups on the page.
This means my editor doesn’t slow down as I build separate features in their own reusable element and when the feature is all finished and tested, I place it into a group on the page. Eventually the editor will be slow when I have added a lot of reusable elements on the same page, but only when I am loading that one page and since the only thing I’m doing there is adding the navigation workflows, it is not much of an issue overall.
Learn More
Boston85719 is an expert Bubbler with a decade experience as an educator. Real name Matthew, he has been actively building SaaS apps, marketplace apps, scheduling apps and more for clients, himself and for sale as templates.
As an official Bubble Bootcamp Instructor, he leads Bubble Bootcamps on a regular basis.
Always willing to offer advice via the Bubble Forum, Matthew also offers Private Personal and Group Training Sessions.
Through his site, NoCodeTrainer, Matthew provides a range of tutorials with editor access to help you jumpstart your Bubble development.
Always accessible you can send Matthew a private message via the forum or send an email directly with your requests.
Be sure to checkout the Stripe Integration Course when you are ready to integrate Stripe payments to start monetizing your application via product sales or subscriptions.
