One page apps load all the app data at once. Page load time will be slightly longer. But, as everything is already downloaded, if you click a nav button that reveals a different page, it is quicker, as all the browser has to do is hide the current page and display the next page. If you have multiple pages, only the current page data is sent to the browser, and when you click a nav button, your browser goes to the new URL, downloads the new page’s data, and displays that.
One thing that is rarely mentioned when people discuss one page apps is they have 2 unique challenges:
The more elements you have on a page, the slower the Bubble editor is. It’s not game breaking… but keep this in mind. You’ll become a lover of “issues_off=true” as it’s the only way some of my pages remain snappy.
One page apps rely heavily on hidden elements. There is no “show all elements” when you open up and start working. You’ll spend a chunk of your time just clicking through and trying to show the exact part you’re trying to work on. It’s fine for a while, but I’ve been doin this for years and it gets annoying when you’re in a time crunch and spend 30 seconds furiously clicking through groups…
However, the big upside is indeed that once the page is eventually loaded, it is snappier to users!
Completely agree on your second point! There is a show all children button if you right click, not not a ‘reveal all children in elements tree’. Might make a suggestion…
it’s just a tradeoff of slower initial load time, vs quicker experience in navigating once the page has loaded. The primary reason why this is overall a benefit is that the network call is one of the slowest parts of the interaction.
fyi I’ve indexed a few single page app resources here Bubble Single Page Apps