For Lovable apps
Put your Lovable app in the App Store and Google Play
BDK Native turns your published Lovable 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 Lovable 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.
Free to try. BDK never needs your code, only your app's address.
Last updated
How it works with Lovable
Publish your app in Lovable.
Use the published address, like yourapp.lovable.app or your own domain. BDK needs that address, not an editor or share link.
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.
Push to everyone needs no code: you send it from your own OneSignal account. Face ID, the camera, in-app purchases and push to one person start from the free @thebdk/native package, called from your app's code. Your backend still sends one-person notifications and decides who has paid. Your AI can add the calls.
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
Tell your 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.
- When a player reaches level 10, vibrate the phone, send a push notification to their friends, open the share sheet so they can post it to their Instagram story, and offer the next level as an in-app purchase.
- When someone books a class, remind them with a push notification an hour before it starts, and let them sign back in with Face ID instead of typing a password.
- When a report finishes, send a push notification to the person who asked for it, show an unread badge on the app icon, and let them send the report with the share sheet.
Your AI adds these with the free @thebdk/native package. Push to one person and in-app purchases still need your backend: it sends the notification and decides 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, published. A lovable.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.
- No access to your code or your Lovable project. BDK only needs 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.
What stays yours
- Your store listings, ratings and reviews. The apps are published from your own accounts.
- Your Lovable project, your code and your backend.
- 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.
Sign-in
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; your app calls it from its code. 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 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. 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 only 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. Uploads still go to your own storage. 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. 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 only.
What Lovable says
Lovable publishes your project as a website. Its publishing docs say: “Lovable does not generate projects in React Native.” They point to two routes: installing your site as a web app (a PWA), or wrapping it as a native app yourself.
Why keep your web app
Lovable has no native route of its own, so you don't need to rebuild your app in React Native to be in the App Store and Google Play. BDK does the wrapping for you: you keep building in Lovable, your accounts and data stay yours, and you get signed builds for both stores.
If you later build a fully native version, it ships as an update to the same store listing: same name, same reviews, and your users just get an update.
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 | $99 one-time | $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.
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.
Prices as of .See pricing
Questions
How do I turn my Lovable app into an iOS and Android app?
Publish it in Lovable and give BDK the published address. 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.
Will my changes in Lovable show up in the app?
Yes. The app loads your live site, so whatever you publish from Lovable 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.
Can I keep my Lovable Cloud or Supabase users?
Yes. 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. Sign in on your phone in BDK Preview to check your own setup; if they sign in with Google, that needs the change in the next answer.
Will Google and Apple sign-in work in the app?
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. Test the sign-in your users actually use in your own build before you submit it.
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 only 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 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 Apple accept my Lovable app?
Nobody can promise that: Apple and Google decide. Apple's guidelines push back on apps that add nothing beyond a website, so give people a reason to install, like push notifications, Face ID or a camera flow wired into what your app does. BDK's native features exist for that.
Docs
See your own app on your phone, free, before you pay anything.