Bubble's Mobile Plugin Editor Hits Public Beta and BubbleGo Is Deprecated: What It Means for Your MVP
Bubble launched the public beta of its mobile plugin editor with full npm support. At the same time, it deprecated BubbleGo. Here is how I'd adjust mobile MVP testing and launch plans as a non-technical founder.
On September 22, 2026, Bubble Product Manager Amy Zhong announced two updates for native mobile development. The mobile plugin editor moved from alpha to public beta. And BubbleGo, the mobile testing app, was officially deprecated. Same topic: BubbleGo’s end and npm in.
If you're a non-technical founder using no-code or vibe-coding to ship an MVP fast, these two changes pull in different directions. The first expands what you can build. The second changes how you test your app before you put it in front of early users and investors. I'll go through both.
What the Mobile Plugin Editor Beta Delivers
The biggest technical change is native support for third-party npm libraries. During the alpha, plugin creators could only use React Native core libraries. In the public beta, they can pull in virtually any package from npm. Same topic: Workflow engine alpha: “end of.
The Bubble marketplace already lists around 700 mobile plugins, and npm support will add new ones much faster. For non-technical builders, advanced native features like specialized device sensors, custom charts, scanning tools, or third-party integrations can now come as off-the-shelf plugins. You won't have to write custom backend or app code for them. A closer look: Expo SDK 57 in Bubble.
Why BubbleGo Was Deprecated and How to Test Now
BubbleGo was the quickest way to preview an app on a physical phone without building a deployment pipeline. But Apple App Store policies no longer allow apps that preview and run arbitrary third-party code. Because of that, Bubble can't submit updates or bug fixes for BubbleGo.
BubbleGo stays installed on existing devices and in the app stores for now. It won't get new features or bug fixes. Bubble now offers two separate workflows to replace it:
- Simulated Device Mode in Web Preview. This mode runs in the browser on a dedicated device simulator instead of the standard React Native for Web layer. According to Bubble co-founder Emmanuel Straschnov, it works on free plans. Sessions may queue when platform demand is high.
- Live Dev Builds on Real Hardware. You install a dev build on a real device through TestFlight (iOS) or Google Play Console (Android). The build stays connected to the Bubble editor, so your changes show up live. This workflow needs an active paid Bubble plan and connected developer accounts. A closer look: Bubble September Roadmap: Official MCP.
Practical Recommendations for MVP Builders
If you want to validate a product concept quickly without spending much, here's how I'd change the rollout plan:
- Use Simulated Device Mode for early iterations. I'd design screens and check user journeys in the browser-based device simulator. You don't need to buy store developer accounts or upgrade your plan right away to test basic flows.
- Don't trust standard web preview too much. It still runs on React Native for Web and can mis-render plugins that use complex third-party npm libraries. If a mobile plugin looks broken there, switch to simulated device mode or start a dev build.
- Budget for a paid plan and store accounts before user testing. If you want to show your app to investors or beta testers on a physical phone, you now need a dev build. Get your Apple and Google developer accounts and a paid Bubble plan into your schedule earlier.
- Add plugins one at a time. In community reports from the beta launch, people noted edge cases, such as intermittent delays with over-the-air (OTA) updates after adding certain npm packages. Add and test new marketplace plugins one by one, and confirm each one is stable before you move on.