I have a Bubble app that has 20 pages. If I’m working in the Bubble editor on page 18, I don’t want the “We just updated this page. Please refresh the page to use the latest version.” to be shown on all other pages. Is this possible?
Or, as an alternative, can we just NOT show any “We just updated this page.
Please refresh the page to use the latest version.”?
Hmm, I’m genuinely curious what I am missing here. If the refresh is necessary no matter what (and that was never in question because that’s how Bubble works), how is the user experience enhanced by hiding the banner and then either refreshing the page “out from under” the user (which could be quite jarring and would honestly be a terrible user experience, in my opinion) or having the user have to refresh the page manually (which they already have to do)? With regard to the latter, that is literally the point of the banner, so if you hide it, how is the user supposed to know they need to refresh the page? Again, just curious what I am missing here.
Hi there, @mikeloc! I completely appreciate your insightful remarks and more than understand the point you’re raising. Allow me to provide a bit more context to my initial suggestion.
In situations like mine, where the Bubble application setup comprises multiple, essentially independent 1-page apps, the dynamics change. Every ‘page’ is, in essence, a separate app, and my model of operation involves users interacting with these individual apps in isolation, on a use-and-close basis.
So, when changes are made to one of these ‘pages’ or 'micro-apps’ (let’s say App No. 18), users of the other apps (the remaining 102 in this case) have no need for an update message regarding changes to App No. 18. Displaying the update message to them, in this context, is counterproductive and can interrupt their experience.
The key point is that in this setup, every single 1-page app always gets loaded afresh by the user. When a user goes to use their desired app, any changes made will have already been incorporated in the background.
I’m not advocating for a blanket removal of the update message, just remarking on its potential redundancy in specific use-cases like mine. I hope this clears up my point of view. I truly value discussions like these since they drive us to think more deeply about user experiences and design choices. Thanks for engaging!