For Bubble apps
Put your Bubble app in the App Store and Google Play
BDK Native turns your live Bubble web app into real iOS and Android apps for your own App Store and Google Play accounts. The apps load your live site, so you keep building in Bubble and every change you deploy shows up in the app, with no store update. Try it free on your phone first in the BDK Preview app, before you pay anything.
Free to try. BDK never needs your editor, only your app's live address.
Last updated
How it works with Bubble
Deploy to live.
Use your live address, like yourapp.bubbleapps.io or your own domain, not the editor link. The address with /version-test is the development version, not the live app your users are on.
Try it on your phone, free.
Press Preview on my phone, paste the address and open your app in the free BDK Preview app. Sign in and use it the way your users do.
Add phone features, if you want them.
Install the BDK plugin, Native apps (bdk), from Bubble's plugin store and use its actions in your workflows: push notifications, in-app purchases, the camera and QR scanning. Your workflows still decide who gets a notification and who has paid.
Order your build.
Pick iOS, Android or both. Then fill in one short form: the app's name, icon, loading screen and your store account details.
Get your builds and submit them.
BDK builds and signs your apps and gives you a step-by-step guide. You submit them from your own Apple and Google accounts, and Apple and Google decide.
Ask for it in plain words
Build it with the BDK plugin's actions in your workflows. For example:
- When a seller gets an offer on a listing, send that seller a push notification, and let buyers scan a QR code on a flyer to open the listing in the app.
- When someone replies to a post, send the author a push notification, let members share the post with the share sheet, and let them take a photo for a new post with the native camera.
- Sell extra credits as an in-app purchase, and save each member's login so they skip the sign-in form next time.
The plugin's actions start the phone side. Your workflows still decide who gets a notification and who has paid.
Closer to native
The details that make an app feel native are built into every BDK app.
Native screen transitions
A new screen slides in, and you swipe back from the edge, like the apps already on your phone. Each screen has its own web view.
Native modals and sheets
A screen slides up, and you close it by pulling it down or tapping close. Sheets can stop at half or full height, each with its own web view.
Permission prompts when they're needed
Camera, photo and location prompts appear by themselves the first time a feature is used.
Status bar
Solid, translucent with blur and your own tint, or transparent.
Your own splash, loading and transition screens
Each set on its own, including animations such as Lottie and SVG.
71 native features in total. Try most of them live in the demo app.Open demo.thebdk.com
What you need
- Your app deployed to live, on bubbleapps.io or your own domain.
- An Apple Developer account for iOS and a Google Play developer account for Android, in your own name.
- No editor access. BDK only needs your live address.
- For push notifications, which are on unless you switch them off: your own OneSignal account (the free tier works) and Firebase project. Switching push off or back on is a new build you submit again.
- For other phone features, the BDK plugin, Native apps (bdk), in your app.
What stays yours
- Your store listings, ratings and reviews. The apps are published from your own accounts.
- Your Bubble app, its data and its workflows.
- Your users, their accounts and your data, on your own backend. BDK doesn't move or copy them. Sign-in and checkout for digital goods may need changes for the app (see the checks below).
- The Android signing key. It comes with every Android build.
Check these on your phone first
Do these in BDK Preview before you buy, on an iPhone and an Android phone if you can.
Your pages on a phone
The app shows the same pages as your site. Open your key pages in BDK Preview and make sure each one fits a phone screen. A layout fix in Bubble shows up in the app too.
Sign-in and login plugins
Sign in, close the app and open it again. Google doesn't allow its sign-in page inside an app's embedded browser, so check any plugin that signs people in with Google on both phones. BDK Preview shows how it behaves, but it doesn't prove your store app's Google or Apple sign-in setup. Saved login is a separate feature: the BDK plugin can save login details so returning users skip the form. It doesn't change how Google's sign-in page opens.
Payments
If you sell with Stripe, walk through a real purchase. Physical goods and real-world services, including real-world subscriptions like a gym or a meal kit, generally keep your web checkout. Digital things used in the app, like credits or a digital subscription, generally must use Apple's and Google's in-app purchases. That's the stores' rule, not BDK's. The BDK plugin's in-app purchase actions start those flows; you set up the products, and your workflows decide who has paid. In BDK Preview, purchases run only against BDK's own sample products; your own products work in your own build.
Uploads, camera and popups
Try your file uploader, the camera and any plugin that opens a popup or a new window, on both phones. For native photo taking and picking, the BDK plugin has Take photo and Select photo elements.
BDK Preview runs your real site, so what works there is strong evidence. It doesn't prove your store app's sign-in or push setup, or how store review will go, and its purchases use BDK's sample products only.
What Bubble says
Bubble now publishes native iOS and Android apps itself. You build separate mobile screens in its mobile editor, and they share your data and backend workflows with your web app.
Why keep your web app
As of October 29, 2026, on Bubble's Starter plan, mobile adds $30 a month: $69 for web and mobile against $39 for web only, billed monthly ($27 a month more on annual billing, paid up front). On monthly billing, that passes BDK's one-time $102 ($99 plus the $3 plugin) in the fourth month, and keeps going. Bubble's route also means building separate mobile screens in its mobile editor, with a monthly limit on mobile builds: 5 a month on Starter after the first three months (10 a month during them; failed builds don't count).
BDK keeps the pages you already have, so you don't design a second set of phone screens; app-level changes, like a new icon, still need a new build. Test, launch and improve with real users on BDK first. Once the app has traction, a fully native version you sign and submit for this same app can ship as an update to the same store listing: same name, same reviews, and your users simply get an update. The Android signing key comes with your BDK build. Bubble's mobile editor is a separate way to design phone screens; check with Bubble whether it can publish to an existing listing.
Bubble's mobile editor makes sense when you want screens designed for phones from scratch.
Compared with other app wrappers
One app on iOS and Android, with push notifications, for the first 12 months.
| BDK Native | Natively (BuildNatively) | Despia | MobiLoud | |
|---|---|---|---|---|
| Plan | Both platforms | Unlimited | Hybrid Pack | Growth |
| Price, first 12 months | $102 one-time ($99 + $3 plugin) | $384 a year, or $49 a month ($699 once for Lifetime) | $498 one-time, with 400 build minutes | $679 a month, billed annually ($8,148 a year) |
| Billing | One-time, with four rebuilds included | Yearly or monthly subscription, or one-time Lifetime | One-time pack | Monthly or annual subscription |
| If you stop paying | There is no subscription to stop | If a monthly or annual subscription lapses, their FAQ says a blocking banner covers the app until you reactivate; Lifetime is separate | No subscription is shown for the pack | Their terms end the license when the paid period ends; their FAQ says you then remove the app from the stores or replace it with another vendor's app |
| Free preview of your own site on a phone | Yes, in BDK Preview | Yes, in Natively Preview, with a limited set of native features | Free watermarked builds; on iPhone they need your own Apple developer account and signing | A free preview of your site is offered; testing native features on a phone isn't stated |
Median also has a free tier for limited use; its Starter plan is a $229 activation, then $179 a year. Its terms limit commercial use on the lower plans, so it isn't priced here. Prices exclude Apple and Google developer fees, taxes and usage charges.
Prices as of , from each company's pricing page.
Try first, pay once
No subscription, no upsells.
You pay once per build purchase. There is no monthly or yearly BDK fee and no hidden charges.
Build and test on your phone, free.
Try native features, push, in-app purchases and your loading screens in BDK Preview before you pay, with up to 20 previews per account. In Preview, push runs on BDK's keys and purchases use BDK's sample products. On iPhone, BDK Preview opens only your own previews; to show your app to clients or early testers, use BDK Preview on Android or the web.
Builds, typically within hours.
We typically deliver builds within hours or overnight. An automated check tells you within 2–3 minutes if anything is missing.
Your web app can move.
Point your app at a new address from your BDK dashboard, with no new store submission: same listing, reviews and installs.
Moving off Bubble is a different step.
Pointing your app at a new address needs no new submission, but moving off Bubble itself may mean rebuilding the web app: Bubble has no code export.
Made for Bubble apps for years.
BDK has delivered over 9,000 iOS and Android builds for Bubble customers.
What it costs
$69 for iOS, $69 for Android, or $99 for both, paid once. Introductory pricing, valid until Thanksgiving. Each purchase includes one build and four banked rebuilds; the rebuilds expire 12 months from payment. Extra rebuilds are $19 and also expire 12 months from payment. Changes to your site never need one. Apple ($99 a year) and Google ($25 once) charge for their own developer accounts. For phone features, the BDK Bubble plugin, Native apps (bdk), is $3 once on Bubble's plugin store, so both platforms plus the plugin come to $102.
Prices as of .See pricing
Questions
Should I use Bubble's native mobile builder or wrap my existing Bubble web app?
Both are real options. Bubble's mobile editor builds native screens you design for phones, sharing your data and workflows. BDK puts the web app you already have in the stores, so you don't design a second set of phone screens; app-level changes, like a new icon, still need a new build. If your pages already work well on a phone, try them free in BDK Preview first.
How is BDK different from other app wrappers?
BDK is a one-time payment: $102 for both platforms, including the $3 plugin, with no subscription. As of October 29, 2026, Natively's Unlimited plan is $384 a year or $49 a month ($699 once for Lifetime), Despia's Hybrid Pack is $498 one-time, and MobiLoud's Growth plan is $679 a month billed annually. Natively lets you try your own site in Natively Preview, with a limited set of native features. Despia offers free watermarked builds; on iPhone those need your own Apple developer account and signing. Prices change, so check each company's pricing page.
Will my Bubble changes show up in the app?
Yes. The app loads your live site, so whatever you deploy to live shows up in the installed apps right away, with no store update. The app itself needs a rebuild when you change what is built into it: its icon or name, the three screens, orientation, permission text, push or deep-link settings, or background audio. You also need one for a newer BDK engine, or when Apple or Google require a new build.
Which Bubble address should my app use?
Your live address, where your real users and data are: yourapp.bubbleapps.io or your own domain. The address with /version-test is the development version, not the live app your users are on, so keep it for trying things. You can point the app at a new address later from your BDK dashboard, with no rebuild.
Do I need the BDK plugin as well as a build?
Only for phone features. The plugin, Native apps (bdk), adds push notifications, in-app purchases, the camera and QR scanning to your workflows. It costs $3 once on Bubble's plugin store. The build is a separate purchase.
Will my current login plugins work in the app?
Test them in BDK Preview before you buy. Email and password sign-in happens on your own pages, so it's the easiest to check: sign in, close the app, open it again. Google doesn't allow its sign-in page inside an app's embedded browser, so check any Google sign-in plugin on both phones. BDK Preview shows how it behaves, but it doesn't prove your store app's Google or Apple sign-in setup. Saved login is a separate feature: the BDK plugin can save login details so returning users skip the form.
Can I keep my Stripe customers and add App Store purchases?
Your Stripe customers stay in your Stripe account, and BDK never needs your Stripe keys. Which checkout you can use is the stores' rule: physical goods and real-world services generally must not use in-app purchases, while digital things used in the app generally must. The BDK plugin has in-app purchase actions; you create the products in App Store Connect and Google Play Console, and your workflows decide who has paid. In BDK Preview, purchases run only against BDK's own sample products; your own products work in your own build.
Docs
See your own app on your phone, free, before you pay anything.