Why Does Bubble Still Require Page Refreshes? A UX Concern

[jayy]

One thing that continues to bug me about Bubble is how every single deployment (no matter how minor the update) triggers a forced full-page refresh for users:

We just updated this page. Please refresh the page to get the latest version. You will not be able to use the app until you refresh.

This really hurts the user experience, especially when they’re in the middle of something. I’ve used countless other web apps, and none of them does this.

To be clear, I’m not looking for workarounds like hiding the notice bar or forcing an automatic refresh. That would just hurt the UX even more. I’m trying to understand why this is still needed, and whether Bubble has plans to improve this experience.

From what I read, there were plans to address this a few years ago, but there has been no news since then.

I feel this is exactly the kind of fundamental user experience issue that Bubble should prioritize improving, rather than diverting resources into half-baked AI features or mobile app solutions.

[boston85719]

My guess is they need to send the updated json file that is the bubble app for the browser to have it.

[randomanon]

Supposedly the work they did on the native mobile editor addresses this, and there’s also supposedly a chance this could make its way to the desktop editor. (According to Bubblecon 2024)

[ihsanzainal84]

Personally i don’t see any issue with this. You shouldn’t be pushing to prod during busy hours in the first place. That’s the bad UX.

Even if Bubble did implement some sort of live update, the risk of disruption does not reduce and you’re going to come back to some sort of banner that says there’s an update.

You’re going to have to find the best time to push updates to reduce the potential disruption to your users.