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 v0 apps
Put your v0 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 v0. 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 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 v0.
Publish your app in v0.
Use the production address Publish gives you, like yourapp.vercel.app or your own domain, not a v0.app chat link or a preview deployment. If it asks for a Vercel sign-in, your users would see one too.
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 QR scanner, in-app purchases and push to one person start from the free @thebdk/native package. Google sign-in goes through BDK's external sign-in, from the same package. Your backend still sends one-person notifications and decides who has paid. Ask v0 to 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 v0, or any AI that edits your code, 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.
When a customer books an appointment, send them a push notification the evening before, skip it if they cancel, and let them sign back in with Face ID instead of typing a password.
When an image finishes generating, send a push notification to the person who asked for it, show an unread badge on the app icon, and when they run out, offer more credits as an in-app purchase.
On the packing screen, let someone scan the shelf barcode with the phone's camera, and show a warning if that item was already packed for another order.
These use the free @thebdk/native package in your app's code. Push to one person, in-app purchases and ticket checks still need your backend: it sends the notification, decides who has paid and marks each ticket as used. For reminders, your backend also matches customers to their phones, sends each reminder at the right time in their time zone and cancels it when a booking is cancelled; BDK gives the app the ability to receive it. Face ID unlocks your own sign-in; it doesn't replace it.
Before you buy.
Check these on your phone first.
Your production address
Open the address in a private browser window, signed out of Vercel. If it asks you to log in to Vercel, the address is protected, even if it's your production address, and your app's users would be asked too. Check your Vercel project's Deployment Protection settings. A vercel.app address with a long code in it is one fixed deployment, so it won't show your later changes. Use the production address Publish gives you.
Sign-in
The v0 changelog says new apps with sign-in and a database start with Better Auth by default; older apps may use Supabase, Clerk or Auth.js. Sign in the way your users do, then 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.
Paid access
If v0 connected Stripe for you, make sure the published app uses your live Stripe account, not a test sandbox, then walk through a real purchase and a cancelled one. 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. Vercel Functions accept requests up to 4.5 MB, so a full-size phone photo may need to go straight to your storage instead. For a native camera or photo picker, BDK has helpers your code can call.
Links from your emails
Tap a password-reset or sign-in link from your inbox on the phone and see where it lands: it may open in the phone's browser instead of the app. For links that open the installed app, set up deep links with Branch or ChottuLink before you order the build.
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.
What v0 says about publishing. Publishing in v0 puts your app on Vercel as a website. The v0 iOS app is where you build, not a store app for your users.
What v0 says
In its deployment docs: “v0 deploys projects to Vercel.” Publishing gives your app a production address on vercel.app or your own domain, and protected deployments can send visitors to a Vercel sign-in.
The v0 iOS app is for makers. The v0 FAQ says it lets you “prompt, generate, and iterate on projects directly from your iOS device.”
The v0 changelog says new apps with a database and sign-in are set up with Neon, Drizzle and Better Auth by default.
Why keep your web app
As of October 30, 2026, the v0 docs describe publishing as a deployment to Vercel, and we found no v0 route of its own to the App Store or Google Play. So you don't need to rebuild your app in React Native to be in the stores. BDK packages the app you already have: you keep building in v0, and you get signed builds for both stores.
The store app opens your hosted website, so the work your app already does on Vercel's servers, like signing people in and saving data, stays where it is. You keep building in v0, and you do not have to turn the site into a separate phone app to be in the stores.
Your v0 and Vercel plans are a cost either way. As of October 30, 2026, the v0 Free plan costs $0 and Plus is $30 per user a month, for building. Hosting is Vercel's: Hobby is $0 but limited by Vercel's terms to personal or non-commercial use, so a commercial app budgets for Pro, from $20 a month plus usage. On top of that, BDK is one payment, with no monthly fee to keep paying.
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 v0 project, your Vercel project and your database stay yours. If you later host the web app somewhere else, point the store app at the new address.
What you need.
- Your app, published to Vercel. The production vercel.app address works; your own domain is optional.
- 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 code, your v0 chats or your Vercel account. BDK needs just the address.
- A Vercel plan that fits your use. Vercel's terms limit the free Hobby plan to personal or non-commercial use, with or without BDK.
- 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's code.
$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 v0 app?
BDK Native turns your published v0 app into real iOS and Android apps for your own App Store and Google Play accounts. The apps load your live site on Vercel, so you keep building in v0 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 v0 app into an iOS and Android app?
Publish it from v0 to Vercel and give BDK the production address: yourapp.vercel.app or your own domain, not a v0.app chat link or a preview deployment, and not an address that asks for a Vercel sign-in. 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 the v0 iOS app the same thing?
No. The v0 iOS app is for you, the maker: the v0 FAQ says it lets you prompt, generate and iterate on your projects from your iOS device. Your users don't install it to use your app, and publishing in v0 puts your app on Vercel as a website. BDK builds signed iOS and Android apps of your own from that published address. You submit them from your own developer accounts; Apple and Google decide.
Will my changes in v0 show up in the app?
Yes. The app loads your live site, so whatever you publish from v0 to your production address 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 sign-in work in the app?
Test it in BDK Preview before you buy: sign in, close the app, open it again, then sign out and reset a password. The v0 changelog says new apps with sign-in and a database start with Better Auth by default; older apps may use Supabase, Clerk or Auth.js, so check what yours uses. 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, and your session has to come back with it. 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 web 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.
Can my store app run on Vercel's free Hobby plan?
Vercel's terms limit the Hobby plan to personal or non-commercial use. If your app sells something or runs a business, put it on a paid Vercel plan, with or without BDK. The store app loads your Vercel site, so it follows whatever plan the site is on, and BDK never needs access to your Vercel account.
Last updated
See your own app on your phone, free, before you pay anything.