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 Base44 apps
Put your Base44 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 Base44. 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 Base44 workspace 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 | Test it first⁵ | 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.
- Base44's docs say its default Google and Apple sign-in fail inside an outside app, and suggest email and password there. 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 Base44.
Publish your app in Base44.
Use the address from Base44's Publish panel, like yourapp.base44.app or your own domain, not a link from the editor.
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, 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. Your 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 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.
The evening before each appointment, send the customer a push notification, and open their booking in the app when they tap it.
Let returning members open their account with Face ID or a fingerprint instead of typing their password, and show the normal sign-in page if that fails.
When someone's AI report is ready, send them a push notification and let them send it on with the share sheet. Sell extra reports as credits through an in-app purchase, and restore past purchases on a new phone.
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, keeps the credit balance and decides who has paid. Links that open the app need Branch or ChottuLink set up before you order the build. Face ID sits on top of your existing Base44 sign-in, so test it in BDK Preview first.
Before you buy.
Check these on your phone first.
Sign-in
Base44's docs say its default Google and Apple sign-in fail in an external wrapper, and suggest email and password. Test sign-in in BDK Preview before you pay. Email and password, or a code typed in the app if your sign-in offers one, is the path to try first. Sign in, close the app, open it again, then reset a password from your inbox. Google doesn't allow its sign-in page inside an app's embedded browser. BDK has an external sign-in helper that opens a sign-in page in the phone's browser, but this page doesn't promise it works with Base44's default Google or Apple sign-in. BDK Preview can show the hand-off, but it doesn't prove your store app's Google or Apple sign-in setup.
Paid access
Base44's built-in Stripe payments run on its Builder plan and up. If you sell with Stripe, walk through a real purchase and check you land back in the app, signed in. 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.
Camera, uploads and the microphone
Base44 documents photo uploads, the camera and the microphone on phones. Try each one in BDK Preview on both phones, and cancel a photo picker halfway too. Uploads still go wherever your app stores them today.
Push notifications
Try sample push in BDK Preview. After receiving your own build, test notifications from your OneSignal account. Base44's built-in push is set up for the store files Base44 makes, so don't assume it reaches a BDK app: test it in your build.
The published address
Open the address from Base44's Publish panel in a private browser tab, signed out, and check it loads without the editor. Base44's docs say renaming your base44.app address breaks the old one at once. If you rename it, point the app at the new address from your BDK dashboard.
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.
Base44's own mobile app, and how it differs. Base44 already turns your published app into App Store and Google Play files, on its Builder plan and up.
What Base44 says
Base44's store guide says: “Your mobile app runs your published Base44 app inside a secure web view.” It makes the iOS and Android store files on the “Builder plan or higher” and signs them; you submit them from your own developer accounts. Its push uses Apple's push service on iPhone, and a Firebase project you create for Android.
Its docs list Face ID and fingerprint login, Apple in-app purchases, Google Play Billing, HealthKit, mobile ad SDKs and full offline use as not supported in that app. The camera, uploads, the microphone and push are supported.
On sign-in, its docs warn that in an external wrapper, Google login “fails with an error such as 403: disallowed_useragent” and Apple login doesn't work either, and suggest email and password there. Google and Apple sign-in are supported in the store files Base44 makes.
Why keep your web app
Base44 already gets your app into both stores, so this is a choice between two routes. BDK adds what Base44's docs list as not supported in its own app: unlocking with Face ID or a fingerprint, and selling digital items through Apple's and Google's in-app purchases, both called from the free @thebdk/native package. If the app is a fitness or wellness app with a real reason to read health data, that read is available too, and you turn it on when you order the build. Skip it when the app merely mentions wellness. You can try Face ID, the camera, push and sample purchases free in BDK Preview on your own phone before you pay anything.
As of October 30, 2026, Base44's Starter plan, the first with a custom domain, is $20 a month billed monthly ($16 a month billed annually), and Builder, the first that downloads store files, is $50 ($40 billed annually). If you'd stay on Starter for the web and keep Builder just for the app, that's $30 a month more, which passes BDK's one-time $99 in the fourth month and keeps going ($288 a year more on annual billing). If your app already needs Builder, for Base44's backend functions or its Stripe payments, mobile adds no plan cost there, and the case for BDK is the features, not the price. Base44's docs gate the download on Builder but don't say what a store app needs after a downgrade, and new store files mean downloading again. BDK is one payment, with no monthly fee to keep paying.
The BDK app opens an address. If you later move your web app off Base44, 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.
Moving the app itself off Base44 is its own project: Base44's code export leaves out your live data, users and secrets, and the exported code still calls Base44's services.
What you need.
- Your app, published from Base44. A base44.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 Base44 workspace or your code. BDK needs just the address, and no particular Base44 plan.
- 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.
$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 Base44 app?
BDK Native turns your published Base44 app into real iOS and Android apps for your own App Store and Google Play accounts. The apps load your live Base44 app, so you keep building in Base44 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 Base44 app into an iOS and Android app?
Publish it in Base44 and give BDK the address from the Publish panel: yourapp.base44.app or your own domain, not an editor link. Try it free in the BDK Preview app on your phone, sign-in first. 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 Base44's own mobile app the same thing?
Partly. On its Builder plan and up, Base44 makes iOS and Android files that run your published app in a web view, with push notifications, and you submit them yourself. BDK is for what that app doesn't cover: Face ID or fingerprint unlock, Apple and Google in-app purchases and reading health data, which Base44's docs list as not supported there. You can try Face ID and sample purchases free on your own phone before you pay BDK once, and your app can point at a new address if you move off Base44. Base44 needs its Builder plan to download its store files; its docs don't say whether you must keep that plan after launch. If you're already on Builder and need none of those features, Base44's own route may be the simpler choice. If your app is already in the stores from Base44's files, check before you order whether a BDK build can update that listing.
Will my Base44 changes show up in the app?
Yes. The app loads your live Base44 app, so whatever you publish from Base44 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 Google and Apple sign-in work in the app?
Don't assume so. Base44's docs say its default Google sign-in fails in an external wrapper and Apple sign-in doesn't work there either; they suggest email and password. Test sign-in in BDK Preview before you pay: email and password, or a code typed in the app if your sign-in offers one, is the path to try first. Google doesn't allow its sign-in page inside an app's embedded browser. BDK has an external sign-in helper that opens a sign-in page in the phone's browser and returns to the app, but this page doesn't promise it works with Base44's default Google or Apple sign-in. 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 Base44 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. Base44's docs list Apple in-app purchases and Google Play Billing as not supported in its own store files. 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.
Do I need Base44's Builder plan for BDK?
No. BDK needs just your published address, and a base44.app address works. Your app may need a paid Base44 plan for its own reasons: your own domain starts on Starter, and Base44's backend functions and built-in Stripe payments need Builder. Your plan's limits, like integration credits, apply inside the app as they do on the web.
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.
Last updated
See your own app on your phone, free, before you pay anything.