Do you ever decide to combine/break apart pages based on the number of workflows/repeating groups?

I’m not sure if pages should be based solely on UI or if there’s ever a time where it makes sense to say “this page has too many workflows - I’m going to separate the functionality into 2 pages” or “this page has almost nothing happening on it - I’m going to turn it into a group/popup on another page”.

I’m not sure what too many workflows/repeating groups/etc. would be - just thinking out loud. Thanks!

My feeling is that it is better to ask the question from a slightly different perspective.

On an “overly complex” page, I’ll ask, "Am I trying to do too much? If so, what can I get rid of? Otherwise, if it is essential, I try to see if I can reduce the number of workflows by more effective use of custom workflows, reusable elements and API workflows.

For the few complex single-page apps within Bubble I’ve developed I’m fairly happy with their performance despite the total number of workflows on the page. Workflow design (along with solid reusable element utilization) is significantly more important than the overall number of workflows.

For example, if I have 5 popups on a page which are all similar in size and function (ie. they have a bit of text and a button), I will consolidate them into one “multi-use” popup and display the relevant group using states. That way I can leverage the same “close” workflow on all popups, set a “when this popup is closed” action that applies universally.

1 Like