BDK Native
- iOS + Android apps$99
Total, once$99
1 build + 4 rebuilds, the rebuilds banked for 12 months
The apps are yours for good. No renewal.
Introductory pricing, valid until Thanksgiving.
For Bolt apps
Put your Bolt app in the App Store and Google Play
Try a sample purchase, the camera, a deep link, Face ID and push on your own phone, free, while you build in Bolt. Pay once when it's right.
- Free on your phone first, before you pay and before an Apple developer account.
- $99 once for both apps. No monthly fee.
- Nothing to lapse. Your app keeps working.
Sample products in Preview. Your own products in your build.
All five run in the free BDK Preview app.
Keep your Bolt project and code private. BDK needs just your app's published address. On iPhone, BDK Preview opens your own previews.
Try it on your phone first.
Natively's own docs say in-app purchases, deep links, the camera and audio don't work in their preview app. All four run in BDK Preview, free, on your own phone (purchases with sample products).
What you can test in each service's free preview, before you pay. From each company's own docs, as of October 29, 2026.
BDK Preview next to Natively Preview.
 BDK Preview | Natively Preview | Median | Despia | MobiLoud | |
|---|---|---|---|---|---|
| Push notifications | Yes¹ | Yes | No shared preview app. You test in a browser simulator, where some native features can't be tested, or in a watermarked build of your own app. | No shared preview app. You test free watermarked builds of your own app. | Their team arranges a preview of your site before purchase. Native-feature testing on a phone isn't documented. |
| Camera | Yes² | No | |||
| Record and play audio | Yes² | No | |||
| Deep links | Yes³ | No | |||
| In-app purchases | Sample products⁴ | No | |||
| Face ID / fingerprint | Yes² | Not documented | |||
| Google / Apple sign-in | Shows the hand-off⁵ | No (social login) | |||
| Your own loading screen | Yes⁶ | No (custom loading screen) | |||
| Needs an Apple developer account to try on iPhone? | No (public TestFlight)⁷ | No (App Store) | Yes ($99 a year) | Yes ($99 a year) | Not documented |
✗ where their docs say it doesn't work. “Not documented” means we found nothing either way. Sources below.
- Push in BDK Preview runs on BDK's own keys; your own OneSignal and Firebase keys are used in your build.
- Phone features that need no account of your own run in Preview, as they will in your build.
- Deep links in Preview run through BDK's Branch / ChottuLink setup, under BDK's branding.
- Purchases in Preview use BDK's sample products; your own products work in your own build.
- BDK Preview can show the hand-off, but it doesn't prove your store app's Google or Apple sign-in setup.
- Your loading screen, in Preview. Your own icon shows in your build.
- On iPhone, BDK Preview opens your own previews. It doesn't prove store review.
Sources, as of October 29, 2026 (15)
Pay once. Not every month.
Like buying a bike instead of renting one every month. BDK is one payment; a wrapper subscription keeps charging.
One payment
If you stop paying: There's nothing to stop. No subscription, no banner, no kill switch. Your app keeps working.
Natively Unlimited, monthly
- Month 1$49
- Month 2$49
- Month 3$49past BDK
So far$147
Or Lifetime, paid once$699
and every month after
Yearly, $384, passes BDK on the first payment.
If you stop paying: Their FAQ says a blocking banner covers the app until you reactivate.
Prices from each company's pricing page as of October 29, 2026; BDK prices as of October 19, 2026. Apple ($99 a year) and Google ($25 once) charge for their own developer accounts with every service. Median: $229 activation, then $179 a year on Starter; its free tier is for limited use.See pricing
Yours to keep.
Your own listing.
Published from your own Apple and Google accounts. Ratings, reviews and installs are yours.
The Android signing key.
It comes with every Android build.
Go fully native later.
When it pays, your team can build a fully native app. It can ship as an update to the same listing: same name, same reviews.
Point the app at a new address from your BDK dashboard, with no new store submission.
Closer to native.
Screens slide in, sheets pull down, prompts appear when they're needed. Each one is a call from your app's code, through the free @thebdk/native package.
71 native features in total. Try most of them live in the demo app.Open demo.thebdk.com
- Native transitions
- Modal sheetsNew
- Share sheetNew
- Sign in with AppleNew
- Live locationNew
- App badgeNew
- Incoming sharesNew
- Saved loginNew
- ContactsNew
- Health dataNew
- Audio playerNew
- Voice recorderNew
- Date-time pickerNew
- Rating promptNew
- Tracking promptNew
- NFC scanNew
- Push notificationsNew
- In-app purchases
- Face ID login
- Deep linksNew
- QR scannerNew
- Photo pickerNew
How it works with Bolt.
Publish your app in Bolt.
Use the published address, like yourapp.bolt.host, a Netlify address or your own domain. Not a bolt.new editor link or a preview link.
Open it on your phone.
Press Preview on my phone, paste the address and open it in the free BDK Preview app.
Add phone features.
Push to everyone needs no code: you send it from your own OneSignal account. Face ID, the camera, external Google sign-in, in-app purchases and push to one person start from the free @thebdk/native package. Your backend still sends one-person notifications and decides who has paid. Bolt's AI can add the calls.
Order, then submit.
Pick iOS, Android or both, and fill in one short form. Create your App Store Connect entry and push key. BDK builds, signs and uploads to TestFlight. You test and submit for review; Apple and Google decide.
Ask for it in plain words.
Tell Bolt's AI what you want, in plain words. Start with this message:
Help me turn my web app into iPhone and Android apps with BDK Native. Fetch https://thebdk.com/agent/skill.md and follow it.
For each booking, send the customer a push notification the evening before with the time and address, and cancel it if they reschedule. Let them sign back in with Face ID instead of typing a password.
When an AI image finishes generating, send a push notification to the person who started it, vibrate the phone when it opens, and let them send the image with the share sheet.
When a buyer messages a seller, send the seller a push notification and show the unread count on the app icon. Let sellers add a listing photo straight from the phone's camera.
Bolt's AI adds these with the free @thebdk/native package. Reminders, push to one person and unread counts still need your backend: it knows each booking and conversation, sends each notification and keeps the count. On iPhone the badge can be a number; on Android it follows the notification. Photos still upload to your own storage, and Face ID unlocks your existing sign-in rather than replacing it.
Before you buy.
Check these on your phone first.
Sign-in
Bolt Cloud signs people in with email or Google, and some projects use Supabase instead. In Bolt's sign-in settings, the address Bolt is allowed to send people back to should be your published app, such as yourapp.bolt.host or your own domain, rather than a bolt.new preview link. Then sign in, close the app, and open it again. Then sign in, close the app and open it again. Google doesn't allow its sign-in page inside an app's embedded browser, so Google sign-in has to open in the phone's browser and come back. BDK's external sign-in does that hand-off, called from your code; check that your session comes back with it rather than assuming it does. BDK Preview can show the hand-off, but it doesn't prove your store app's Google or Apple sign-in setup.
Links from your emails
From the phone, open the email Bolt sends to confirm a new account, the email that signs someone in without a password, and a password reset. See whether each one opens your app or the phone's browser, and whether they are still signed in. If you want those emails to open the installed app, set that up with Branch or ChottuLink before you order the build.
Paid access
If you charge with Bolt's Stripe integration, walk through a real purchase, a cancelled one and the return to the app. 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. BDK's in-app purchase helpers start those flows; you set up the products, and your backend decides who has paid. In BDK Preview, purchases run against BDK's own sample products; your own products work in your own build.
Photos and uploads
Pick a photo, take one with the camera and upload it, on both phones, then check the file landed in your Bolt Cloud storage with the access you meant: Bolt's docs advise checking whether a bucket is public or private. Uploads still go to your own storage.
Your live address and plan
The live app is your bolt.host address, your Netlify deploy or your own domain; bolt.new and editor preview links are not. The app opens that live site, so your Bolt plan's limits still apply: on the Free plan, Bolt's billing docs say the site can stop serving when the month's bandwidth or requests run out, and the app stops with it.
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.
Bolt's own mobile app, and how it differs. Bolt's mobile route is a separate Expo app, best picked at your first prompt.
What Bolt says
Bolt's Expo guide says: “Use Bolt with Expo to build iOS and Android apps from a prompt.” It advises choosing mobile in your first prompt, and warns that projects created for web are hard to switch over to mobile.
For a mobile project, Bolt's Device Preview shows a QR code that opens the app in Expo Go on your phone. The guide then downloads the project and builds it with Expo's EAS tools, for TestFlight and Google Play testing from your own developer accounts.
Web apps publish on Bolt Cloud to a bolt.host address, on Free and Pro, with Netlify as an optional route. A custom domain needs Pro.
Why keep your web app
Bolt's Expo route is real, reaches both stores and suits an app you start as mobile. Moving your existing Bolt web app to Expo can mean adapting its screens and testing a new mobile version; Expo can share code across web and mobile, while BDK keeps the published web interface you already have. You keep building in Bolt, and you get signed builds for both stores.
Expo's own docs list what Expo Go, the preview Bolt uses for mobile, can't test. “The FaceID authentication for iOS is not supported in Expo Go.” To test real store purchases, push notifications or links that open your installed app, Expo says you make a development build, a test version of your own app, instead of using Expo Go. Expo Go does run the camera and audio. BDK Preview runs push, Face ID, deep links and sample purchases around your live site, free, on your own phone, before you pay; it uses BDK's keys and sample products, so your own setup still gets tested in your build.
Your Bolt plan is a cost either way. As of October 30, 2026, Bolt's Free plan publishes to a bolt.host address, and Pro, the first plan with a custom domain, is $25 a month, or $216 a year in Bolt's annual billing example. Bolt's docs list no paid plan for its Expo route, and Expo's Free plan includes store builds and submission, in a lower-priority queue; its Starter plan is $19 a month plus usage. So the difference is the work of adapting your app. Expo's Free plan can take a mobile project to both stores with no extra subscription, in a lower-priority queue, with 15 iOS and 15 Android builds. BDK is a separate one-time payment for packaging the web app you already published.
If you leave Bolt later, the app keeps working: move the site, then point the app at the new address from your BDK dashboard, with no new store submission.
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.
Your Bolt project and your code stay yours. If you move the web app to another host later, Bolt Cloud's database and sign-in don't move with it by themselves; point the app at the new address from your BDK dashboard.
What you need.
- Your Bolt web app, published. A bolt.host address works; a Netlify address or your own domain works too.
- An Apple Developer account for iOS and a Google Play developer account for Android, in your own name.
- For iOS: create your App Store Connect entry and push key. BDK builds, signs and uploads to TestFlight. You test and submit for review; Apple and Google decide.
- No access to your Bolt project or your code. BDK needs just the 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 free @thebdk/native package in your app.
- If you started a Bolt mobile project with Expo instead, that is already a native app, with its own route to the stores.
$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.
Prices as of .See pricing
Questions
What does BDK Native do with a Bolt app?
BDK Native turns your published Bolt 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 Bolt and every change you publish 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.
How do I turn my Bolt app into an iOS and Android app?
Publish it in Bolt and give BDK the published address: yourapp.bolt.host, your Netlify address or your own domain, not a bolt.new editor link. Try it free in the BDK Preview app on your phone. When it works the way you want, order a build: BDK makes signed iOS and Android apps, and you submit them from your own Apple and Google developer accounts.
Isn't Bolt's own mobile app the same thing?
No. Bolt's mobile route builds a separate Expo app, and Bolt advises choosing it at your first prompt. It's a real route to both stores, and it fits an app you start as mobile. If you already have a Bolt web app that works, BDK puts that same app in the stores, so you keep the interface you already have instead of adapting its screens for a new Expo version. Expo Go, the preview Bolt uses for mobile, runs the camera and audio, but Expo's docs say it can't test Face ID on iPhone, real in-app purchases or remote push. BDK Preview runs push, Face ID, deep links and sample purchases around your live site, free, on your own phone.
Will my changes in Bolt show up in the app?
Yes. The app loads your live site, so whatever you publish from Bolt 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.
Will my Bolt Cloud or Supabase sign-in work in the app?
Test it in BDK Preview before you buy: sign in, close the app, open it again, then log out and reset a password. The app opens your live site, so it uses the same backend and the same accounts as your website; BDK doesn't move or copy your users. Google doesn't allow its sign-in page inside an app's embedded browser, so Google sign-in has to open in the phone's browser and return to the app. BDK's external sign-in does that hand-off, for Apple sign-in too; your app calls it through the free @thebdk/native package. BDK Preview can show the hand-off, but it doesn't prove your store app's Google or Apple sign-in setup.
Can I keep charging with Stripe in the App Store app?
For physical goods and real-world services, including real-world subscriptions like a gym or a meal kit, yes: your Bolt Stripe checkout is the right path, and it's the same page inside the app. 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. BDK's in-app purchase helpers start those flows; you create the products in App Store Connect and Google Play Console, and your backend decides who has paid. In BDK Preview, purchases run against BDK's own sample products; your own products work in your own build.
How is BDK different from other app wrappers?
BDK is a one-time payment: $99 for both platforms, 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 Preview excludes in-app purchases, deep links, the camera and audio; Median and Despia have no shared preview app. 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 Apple accept my Bolt app?
Nobody can promise that: Apple and Google decide. A Bolt app that is a thin brochure is the weak case. A booking app, a marketplace, or a tool people open every week is a stronger one when the phone adds something the site does not: a reminder before an appointment, Face ID on the login they already use, or a camera step inside a job they already do.
Last updated
See your own app on your phone, free, before you pay anything.