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 Replit apps
Put your Replit 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 Replit. 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 Replit project 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 Replit.
Publish your app in Replit.
Use the address Replit shows under Publishing, like yourapp.replit.app or your own domain. A replit.dev address is the workspace's development address, not your live app.
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, external sign-in, the camera, 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. Replit Agent or your own 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 Replit Agent, or the AI you build with, 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 client's proof is ready, send them a push notification, and let them approve it with a tap that records the approval on your site.
When a client books an appointment, remind them with a push notification the evening before, and let them scan the QR code at the front desk to check in.
Let sellers sign back in with Face ID instead of typing a password, take photos of an item with the phone's camera to list it, and get a push notification the moment someone makes an offer.
Your AI adds these with the free @thebdk/native package. Push to one person, check-ins and uploads still need your backend: it sends each notification, checks each code and stores each photo. Face ID unlocks your own sign-in; it doesn't replace it.
Before you buy.
Check these on your phone first.
The published address
Give BDK the address from Replit's Publishing tool, on replit.app or your own domain, never a replit.dev address or an editor link. Replit's docs say a published app on the free Starter plan goes offline after 30 days unless you republish it. The store app opens that address, so keep it published.
Sign-in
Sign in on your published app the same way a customer does, then close the app and open it again. Use a real customer account on the published address, rather than an account you created while the app was still in the editor. If Google sign-in is involved, it has to open in the phone's browser and come back, and you should still be signed in after it returns. Ask Replit Agent to wire that return into the sign-in you already use, then try it before you pay. 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 opens Google sign-in in the phone's browser and brings the person back to your app; 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 Replit's Stripe integration, test on your live Stripe setup, not the sandbox: walk through a real purchase, then a cancelled one, 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.
Photos and uploads
Pick a photo, take one with the camera and upload it, on both phones. Check it is saved wherever your app stores files, such as Replit App Storage, and comes back for the right user. 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: in the app, or in the phone's browser. 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.
Replit's own mobile app, and how it differs. Replit can also build a native interface for your app in React Native, with phone screens of its own.
What Replit says
Replit builds mobile apps in React Native with Expo. Its docs say they use “platform-native UI components, not a webview”, and connect to a server Replit hosts for your data and backend.
Replit's guided publishing builds your iOS app in the cloud and uploads it to TestFlight from your own Apple account; you finish the release in App Store Connect. Its docs also say: “Publishing to Google Play is not yet supported by Replit.”
To try the app on a phone, you scan a QR code with Expo Go; paid plans add an iOS simulator and an Android emulator in the editor. Replit's RevenueCat setup can simulate purchases in Expo Go without charging.
Why keep your web app
Replit's own route is a real one: a native interface in React Native, sharing your backend. If your Replit web app already works well on a phone, BDK keeps it as the app. You don't build a second set of phone screens and keep them in step with your website: every change you publish reaches the site and both store apps.
You can try push and Face ID free on your own phone, on the site you already have, before you pay. Expo's own docs say remote push notifications sent from your server need a development build, not Expo Go, and that “FaceID authentication for iOS is not supported in Expo Go.” Replit's Expo Go preview does handle the camera, audio and simulated purchases.
One order gives you signed builds for both stores. Replit's built-in publishing flow currently centers on iOS; Android apps can still reach Google Play through Expo's own tools and your Play Console.
This isn't a price argument against Replit. As of October 30, 2026, Replit Core is $20 a month, or $18 a month billed annually. If you're already on Core, Replit's own mobile route adds no base plan fee. Your Replit plan is a cost either way; on top of it, BDK is one payment for both stores, 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 Replit project, your code and your backend stay yours. Moving your hosting off Replit is its own project; once the web app runs at a new address, the store app can follow it.
What you need.
- Your app, published from Replit. A replit.app address works; your own domain is optional. A replit.dev address won't do: it is the workspace's development address.
- 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 Replit project or your code. BDK needs just the published 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.
$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 Replit app?
BDK Native turns your published Replit 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 Replit 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.
Isn't Replit's own mobile app the same thing?
No. Replit's mobile route builds a native interface in React Native, with phone screens of its own that sit alongside your web app and share its backend. BDK puts the web app you already published in the stores, so there is one interface to keep up to date. You can try push and Face ID with it free in BDK Preview; Expo's own docs say remote push needs a development build rather than Expo Go, and that Face ID on iPhone isn't supported in Expo Go. BDK builds for both stores from one order, while Replit's built-in publishing flow currently centers on iOS; Android apps reach Google Play through Expo's own tools. If you're already on Replit Core, its mobile route adds no base plan fee, so the difference is the work, not the price. If you want phone screens designed from scratch, Replit's route makes sense.
Will my changes in Replit show up in the app?
Yes. The app loads your live site, so whatever you publish from Replit 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 Replit address do I give BDK?
The one Replit's Publishing tool shows: yourapp.replit.app, or your own domain once you connect it. A replit.dev address is the development address of your running workspace, not your live app, and an editor link isn't your app either. On the free Starter plan, Replit's docs say a published app goes offline after 30 days unless you republish it. If you move to a new domain later, point the app at it from your BDK dashboard, with no rebuild.
Will my Replit sign-in work in the app?
Test it in BDK Preview before you buy: sign in on your published app, close the app, open it again, then log out and reset a password. Replit's docs say sign-in you add now defaults to Clerk on Starter, Core and Pro and to Replit Auth on Enterprise, and existing apps keep what they have, so check the one your app really 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 opens Google sign-in in the phone's browser and brings the person back to your app; your app calls it through the free @thebdk/native package. Your developer or AI must also make sure the person is signed in to the app when they come back. 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 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 Replit app?
Nobody can promise that: Apple and Google decide. Replit's own mobile route builds real phone screens, which is one way to give the app a reason to exist. If you keep your website as the app, give people a reason to install that too: a reminder they would otherwise miss, Face ID on a login they use every week, or a check-in step at the front desk.
Last updated
See your own app on your phone, free, before you pay anything.