Hi everyone,
I’m reaching out to the community to get some feedback and share my experience regarding Bubble’s native mobile capabilities.
For context, we run a live business with a native mobile app built on Bubble. We’ve invested significant capital into marketing to drive user acquisition. Overall, I really appreciate the mobile editor—the features, customization, and flexibility Bubble provides are more than enough for our core business needs.
However, we are facing a critical production issue that is putting our entire business at risk:
-
The Problem: At random times, the app suddenly behaves as if it’s “offline.” The home page enters an infinite loading state, making the app completely inaccessible to users.
-
The Process: The only workaround we’ve found is generating a brand-new build and pushing it to the stores, then praying it fixes the bug.
-
The Consequence: Because of Apple and Google review times, our users are locked out for 1 to 2 days every time this happens. Just last week, our app was completely down for 5 full days while waiting for a resolution and response from Bubble support.
For a live company spending money on marketing, having users unable to access the app for days with zero control on our end is an absolute nightmare. The financial and reputational impact is becoming too heavy to bear.
I’m at a point where I’m seriously considering rebuilding the entire mobile app on another stack simply to have full control over our infrastructure.
I’d love to hear from other founders and developers running native apps on Bubble:
-
Have you experienced similar “infinite loading” or app-breaking bugs on native mobile?
-
How do you handle critical production outages when waiting for store approvals isn’t fast enough?
-
For those running high-stakes/paid-marketing mobile apps, are you staying on Bubble Native, or did you end up using wrapper solutions (like BDK, Natively, Jasonette) / migrating to Flutter/React Native?
Looking forward to hearing your thoughts and experiences!