Now in public beta: Mobile plugin editor. Plus important BubbleGo update

UPDATE SEPT 29 2026

Dedicated users: Once your instance is updated from Dedicated Manager, you’ll be signed in to the web simulator automatically and can start previewing your mobile apps in the browser. If you don’t run updates yourself, ask your instance admin to install the latest one.


Hi everyone,

I’m Amy, a product manager on Bubble’s mobile team.

Today, we’re moving the mobile plugin editor from alpha to public beta. We’re excited to finally open it up to everyone!

Depending on how you use Bubble, here’s what’s changed.

What’s new

Third-party library support: When we opened the alpha, developers could only build with core React Native libraries. That covered a lot of ground, but it also meant some native functionality was out of reach simply because the library it depended on wasn’t part of React Native’s core set. Starting today, that limitation is gone: You can now build a native mobile plugin with any third-party npm library. Learn more about building plugins here →

Previewing and testing:

There are two new ways to preview a mobile app as you build:

  • Dev builds: Preview and test your app on a real device, in real time.

  • New Simulated device mode in web preview: Previewing your mobile app in the browser with a Simulated device mode.These two methods will take the place of BubbleGo.

Deprecating BubbleGo

As of today, September 22, we’re officially deprecating BubbleGo. Apple’s App Store policies no longer allow preview apps, which includes BubbleGo. As a result, we can no longer submit updates or bug fixes.

BubbleGo isn’t being pulled from the app stores, and existing installs will keep working as they do today. But since we can’t update it, BubbleGo won’t reflect new features or bug fixes we ship going forward. Dev builds are now the way to preview and test your app on a real device.

What is a dev build?

A dev build is a version of your native mobile app that you install directly on your own device. It looks and runs like your real app, but stays connected to the Bubble editor so changes you make show up on your phone right away.

A dev build allows you to test your app’s full functionality, including native features and any plugins your app depends on, because it’s compiled from your app specifically. That makes it the most accurate way to preview and test your app on a real device.

Note: Creating a dev build requires connecting your app to the App Store and/or Google Play Store, since it’s delivered through TestFlight or the Google Play Console. This means dev builds are only available on paid plans.

You can create a dev build from Settings → Manage builds and live versions → + Dev build. Full setup instructions can be found here.

What is the difference between web preview and simulated device mode?

The standard web preview uses React Native for web to approximate your app in the browser; this is fast, and fine for most day-to-day building. But some plugins, especially ones built with third-party libraries, don’t render accurately through that approximation.

Simulated device mode is a new option within web preview that renders your app through an actual device simulator instead of an approximation, giving you a much better idea of how your app actually looks and behaves on a real device when you’re using certain plugins. If Bubble identifies that your app uses a plugin that would render better in Simulated device mode, you’ll see a prompt suggesting the switch. You can also switch manually anytime from the device dropdown in the toolbar.

Note: During high-traffic periods, you may be placed in a queue to use Simulated device mode. If you’re on a paid plan, we suggest using a dev build instead of Simulated device mode to preview and test your app. It’s the most accurate preview of your app’s functionality, and you can avoid any wait times.

What this means for you

If you build mobile apps:

*Your mobile app is fully customizable *and your web preview is significantly more accurate now, especially if you have certain plugins installed. We’re already at ~700 mobile plugins, and there are more on the way. Opening up third-party library support unlocks a much wider range of plugin capabilities, so expect the native plugin library to keep growing from here.

Check out this post on the blog for a closer look at a few plugins, and browse the full library at bubble.io/plugins.

If you’re a plugin developer:

This is the update we know a lot of you have been waiting for: You can now build native mobile plugins using any third-party library, not just React Native’s core set. If there’s an npm package that does what you need, it’s fair game.

We built this because the audience for native mobile functionality keeps growing. More builders are shipping mobile apps on Bubble, and they’re asking for capabilities that go beyond what’s available out of the box. As always, you can publish your plugin to the marketplace and charge for your work.

Let’s see what you build

We think opening up third-party libraries is going to meaningfully expand what’s possible for native mobile plugins, and we can’t wait to see the results. If you’re building something, tell us about it below. And if you’re a mobile builder with a specific native feature you wish existed, share that too. This feedback is helpful to signal what developers should build next.

Start building in the plugin editor, read more on the blog, and browse what’s already out there at bubble.io/plugins.

— Amy and the mobile team

Can I send a developer build to test the app’s features without being on a paid mobile plan?

@gabriel15

Hi, I’m trying to add a third-party React Native library to my mobile plugin. The documentation mentions an “Additional libraries” section under the Shared tab, but I can’t find it in my plugin editor.

Is this feature already available, or do I need to enable something first?

Great news, thank you!

One question: are drag gestures supported now? The react gesture library was available before, but it would simply fail if trying to use gestures other than tap.

Thank you very much,

Jonah

Apologies. It should be available now. Can you check again?

It should be available but we are testing it internally again and will get back to you

Thank you very much :slight_smile:

Yes, it’s visible now! thanks!

Hi @amy.zhong I’ve never seen this error message before:

Is this a general error message i.e my old code is incompatible or am I forced to use a dev build?

Have a great day,

Jonah

Hi Jonah! Where are you seeing this message? If it’s a 3rd party plugin, you’ll need to test in a new build/dev build

It’s my plugin that was working on web preview before. When I run an action that prompts the user to select a file, I get that error message.

What’s the plugin? Did you make a recent update that included a 3rd party library?
Would you mind file a support ticket so we can take a closer look? Thank you!

Great update, Amy! Loving the progress to the native mobile side of Bubble.

QQ: any reason logging into a Dev Build and/or using the simulated browser experience wouldn’t work for dedicated? I’m running into some issues (reported as a bug already).

Thanks John! Yes, we are aware that the experience on dedicated accounts isn’t that great. We’ll have an update ready by Monday.

The third-party npm support is a big improvement for plugin developers. I also like the move to dev builds for real-device testing, since testing native features on an actual device should catch issues that a browser preview can miss.

Thanks for shipping this. Being able to add third-party npm packages opens up a lot we couldn’t do before.

Two issues I’ve hit since adding a package:

  1. OTA updates get stuck. Once a third-party npm package is added, updates never reach users.
  2. New builds fail. I tried a full build instead, but it fails with:

Module mapping check failed

So right now there’s no way to get the update out, either by OTA or a new build.

Sorry to hear that. Would you be able to file a support ticket including your app ID and the package you’ve added so we can take a closer look?

Thanks for following up, Amy.

I raised a ticket around 2 hours ago. A quick update: The new build deployment error worked itself out after 20 minutes. I was able to deploy a new build and my plugin with a third-party npm package is working as expected.

Just the OTA update issue remaining.