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 Claude Code apps
Put your Claude Code 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 Claude Code. 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 repo and your source code private. BDK needs just your app's live HTTPS 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 Claude Code.
Deploy your app.
Ship it the way you already do, to Vercel, Netlify, Cloudflare, Railway or your own server. BDK needs the public HTTPS production address, never localhost or a preview behind a login.
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 write and send it in OneSignal, on your own account. Everything else comes from one free npm package, @thebdk/native, and Claude Code can install it and write the calls. That covers the camera, Face ID, in-app purchases and external Google sign-in. Notifications to one person and the record of who has paid stay with your backend.
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.
Paste this into Claude Code from your project folder first, then ask for features in plain words:
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 learner's daily streak is about to break, send them a push notification at 8 pm their time, show how many reviews are due on the app icon, and let them record their pronunciation with the microphone.
Add a Scan receipt button that photographs a receipt with the phone's camera, let people unlock the app with Face ID, and send the month's expense report as a PDF from the share sheet.
Let new members invite people from their phone's contacts, send the inviter a push notification when someone they invited joins, and sell Pro as an in-app subscription that restores on a new phone.
Claude Code writes the free @thebdk/native calls for the microphone, the camera, Face ID, the share sheet, contacts and purchases. Your app still has to build the expense-report PDF and send and track the invitations; BDK doesn't do either. Streak reminders, push to one person, the due count and the Pro subscription still need your backend: it knows each streak and each invite, sends each notification, keeps the count and decides who has paid. iPhone can show the due count as a number on the icon; Android shows its badge with the notification. Receipt photos and voice recordings upload to your own storage, Face ID is a gate on your own sign-in rather than a new one, and contacts are read with the user's permission.
Before you buy.
Check these on your phone first.
Your live address
Load the live URL in a phone browser that isn't signed in to your host: the app sees exactly what a stranger sees. Vercel can put a login in front of a deployment, and new Netlify sites can start private. Branch deployments and preview addresses aren't your live app. Vercel's free Hobby plan is for personal, non-commercial projects, so check that your plan fits an app in the stores.
Sign-in
Your website already has a sign-in system, whether Claude Code built it with Supabase, Clerk, Firebase or its own code, and the app uses that same system. Test that people can sign in and stay signed in after swiping the app away and reopening it. Google doesn't allow its sign-in page inside an app's embedded browser; the sign-in has to happen in the phone's browser, then come back. Ask Claude Code to call BDK's external sign-in for that round trip, then confirm your session really survives it. BDK Preview can show the hand-off, but it doesn't prove your store app's Google or Apple sign-in setup.
Emailed links
Request a password reset, a magic link and a sign-up confirmation, then open each email on the phone. A link can land in the phone's browser rather than your app, leaving you signed in there instead. Your sign-in provider's settings should list your live address as the site URL, not localhost. Links that open the installed app need Branch or ChottuLink deep links, set up before the build is ordered.
Paid access
Run one real Stripe payment inside the app and one abandoned checkout, and watch where each one returns you. 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. Claude Code can call BDK's in-app purchase helpers for those; the products are yours to set up, 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.
Uploads and the camera
Try every file input on both phones: choose an image from the library, shoot a new one with the camera and send a large file. Check that each one lands in your storage for the right user, and that a denied camera permission doesn't break the page. Files keep going to your own storage.
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.
Claude Code's own route to the stores, and how it differs. There's no Claude Code store service. The native route is code you ask it for, like a second, separate app in React Native and Expo.
What Claude Code says
Anthropic's overview calls Claude Code an “agentic coding tool”: it reads and edits your project and runs commands from your terminal, your IDE, the desktop app or the browser.
Claude's mobile guide describes the Claude app on your phone as “a client for Claude Code sessions rather than a place where code runs.”
Claude Code Desktop has an iOS Simulator pane, in public beta on Pro, Max, Team and Enterprise plans. It needs a Mac with Xcode and runs in local sessions, not cloud ones.
Why keep your web app
Claude Code can take you to the stores more than one way. Ask it for a React Native app with Expo and it can write one; Expo's tools then build it and submit it to both stores. If you ask Claude Code for a separate React Native app, with its own screens, those screens sit next to your website and a change can land in two places. Expo can also put parts of your existing web UI inside a native app, so how much you rebuild depends on how you ask for it. You can also have Claude Code help you build a shell that loads your website, and then the native project and its releases are yours to keep up. Your backend can stay shared, but each screen change then lands in two places. Claude Code can also help you build a web shell of your own that reuses your web interface; then its native project, plugins and releases are yours to keep up. With BDK the store apps open the site you already deploy, and BDK does the packaging and signing: one codebase, one place for Claude Code to work, and signed builds for both stores.
Expo is candid about what Expo Go, its free preview app, can't run. On Android, for remote push: “A development build is required to use push notifications.” For store purchases: “In-app purchase libraries require configuring custom native code.” On iPhone: “The FaceID authentication for iOS is not supported in Expo Go.” Expo Go does run the camera and audio, and a development build of your own closes those gaps once you set it up. In BDK Preview, your live site already has deep links, push, Face ID and sample purchases to try, free, on your phone, before you spend anything. Those run on BDK's keys and sample products, so your own accounts get their test in your build.
Signing is BDK's job: BDK builds both apps and signs them, and you never open Xcode or export a certificate. Expo's cloud builds also work without a Mac and can manage signing, so the real gap is upkeep: a native project has its own dependencies and SDK upgrades, while a change to your web app needs no new build at all.
Claude Code is a cost either way, and it isn't your host. As of October 30, 2026, Claude Pro, the first individual plan with Claude Code, is $20 a month, or $200 a year billed annually. Expo's Free plan includes 15 iOS and 15 Android builds and store submission; Starter costs $19 a month plus usage. On fees, the Expo route can cost nothing extra: Expo's Free plan includes those builds and store submission. What it costs is the work you keep up, whether that is mobile screens next to your website or a native project of your own. BDK is a separate one-time payment, and your Claude plan and your host stay yours to pay.
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.
Claude Code is not where your site is hosted. Your project stays in your repo, and the live site stays on Vercel, Netlify, Cloudflare, Railway, or your own server. If you change hosts, point the app at the new address from your BDK dashboard. Switch hosts whenever you like and give the app its new address from your BDK dashboard.
What you need.
- Your web app on a public HTTPS address that opens without a hosting login. Your host's free 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.
- BDK never sees your source. It needs just the address; Claude Code makes any code changes in your own project.
- 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.
- Phone features beyond push to everyone: the free @thebdk/native package from npm, which Claude Code can install and wire up.
- If Claude Code already built you a React Native or Expo app, that one is native already, 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 Claude Code app?
BDK Native turns your deployed Claude Code web app into real iOS and Android apps, published from your own Apple and Google developer accounts. Each app opens your live site, so whatever Claude Code ships to production reaches your users' phones with no store update. Before paying anything, try it free on your own phone in the BDK Preview app.
How do I turn a web app built with Claude Code into iOS and Android apps?
Three moves. Get the web app live on a public HTTPS address, then paste that address into BDK and open it in the free BDK Preview app on your phone. When you're happy, order the build; BDK hands back signed iOS and Android apps for you to submit from your own Apple and Google accounts. From then on every deploy reaches the installed apps at once, 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't Claude Code just build me a native app?
Yes, and for a product you start as mobile it's a good choice: Claude Code writes the React Native code, and Expo's tools build and submit it for both stores. If you already have a working web app, choosing a separate React Native interface means maintaining mobile screens alongside your website. Claude Code can also help you build a web shell that reuses your web interface, and then the native project and its releases are yours to maintain. BDK reuses your web interface too, and manages the packaging and signing for you. Before you pay, BDK Preview lets you try push, deep links, Face ID and a sample purchase on your own phone. Expo Go handles the camera and audio, but Expo's docs say Android remote push, store purchases and Face ID on iPhone need a development build of your own.
Do I need a Mac or Xcode to put my app in the App Store?
Not with BDK. BDK builds and signs both apps, so you don't install Xcode or manage signing certificates. Your part for iOS is creating the app's entry in App Store Connect, giving BDK your App Store Connect upload key (the .p8 file) in the BDK portal, and adding your own push accounts if you keep notifications on. Then you test the build in TestFlight on an iPhone and submit it for review. To be fair to the Expo route, Expo's cloud builds don't need a Mac either; Claude Code Desktop's iOS Simulator does, with Xcode.
Will Google sign-in and my existing sign-in system work inside the app?
Find out in BDK Preview first. Sign in, close the app completely, reopen it, then sign out and try a password reset. The app runs your live site against the same backend, so your users and their logins are the ones your website already has; BDK doesn't copy or move anyone. Google doesn't allow its sign-in page inside an app's embedded browser; the sign-in has to happen in the phone's browser, then come back to the app. That round trip is what BDK's external sign-in does, for Apple sign-in too, and Claude Code can connect it to the sign-in system your website already uses, 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 still take Stripe payments in the store apps?
Yes, when you sell physical goods or real-world services, real-world subscriptions like a gym or a meal kit included: keep Stripe, and the app shows the same checkout page your site does. Digital goods people use inside the app, like credits or a digital subscription, generally have to go through Apple's and Google's in-app purchases; the stores set that rule, not BDK. For those, Claude Code can call BDK's in-app purchase helpers; the products themselves are yours to create 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 an app made from my web app?
Apple and Google make that call, and no one can promise it for them. Apple's guidelines say: “Your app should include features, content, and UI that elevate it beyond a repackaged website.” So hand people a reason to install it: a reminder that brings them back, Face ID on a login they use every week, or a scanner in a real workflow. Ask Claude Code to wire those into what your app already does.
Last updated
See your own app on your phone, free, before you pay anything.