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 Framer sites
Put your Framer site 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 Framer. 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 Framer project private. BDK needs just your site's 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 Framer.
Publish your site in Framer.
Use the live address from the Publish panel: a framer.app or framer.website address, or your own domain. Not a framer.com editor link, a staging address or a version link.
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, in your site's custom code. Google sign-in goes out to the phone's browser and back through BDK's external sign-in. Your backend or automation still sends one-person notifications and decides who has paid.
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, or whoever adds your site's custom code, what you want in plain words. An AI can 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 new issue of the publication goes up, send members a push notification, show how many unread issues are on the app icon, and let them open the latest one with Face ID.
When someone saves a talk on the schedule, remind them an hour before it starts, and cancel the reminder if they drop it.
When a place someone saved in our directory posts a new offer, send them a push notification, open that listing straight in the app from the link, and let them pass it on with the share sheet.
These start from the free @thebdk/native package in your site's custom code. You can send a push by hand from OneSignal; sending one when a lesson or an offer goes live, or the evening before a booking, needs an automation of your own. Outseta, Thenty or FrameAuth still handles sign-in and sessions, and your backend still checks each ticket and knows who saved what.
Before you buy.
Check these on your phone first.
Your custom code
Framer's help says custom code added in Settings doesn't appear in its preview, so your phone-feature calls won't show up in the editor. Publish, open the published site in BDK Preview and try each feature. Then go to another page and back, and try them again.
Member sign-in
Framer's publishing docs show no member sign-in of its own, so members sign in through a plugin such as Outseta, Thenty or FrameAuth. Sign in, close the app and open it again, then log out and reset a password. Memberstack's docs list Framer among builders its standard setup doesn't support, so check before relying on it. 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 it in the phone's browser and returns to the app. Whoever adds your site's code has to connect that to your sign-in plugin, so the member is signed in when they return; test that before you buy. 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 Outseta or Thenty charges members with Stripe, 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 or membership service decides who has paid. In BDK Preview, purchases run against BDK's own sample products; your own products work in your own build.
Menus and effects on a real phone
Framer's help notes that a menu can work in its preview but not on a phone, and that background blur can look different once published. Open the menu, scroll your heaviest pages and fill in a form with the keyboard up, on both phones.
Links from your emails
Tap a password-reset or sign-in link from your inbox on the phone and see where it lands. If you want those links to open the installed app, set that up with Branch or ChottuLink before you order the build. If that setup asks you to put a small file on your own domain, Framer hosts that kind of file on Pro and Enterprise. On Basic, ask them whether the link can work without the file.
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 Framer says about publishing. Framer's publishing docs describe websites; we found no app-store route of its own.
What Framer says
Framer publishes your project as a website. Its publishing guide says: “Your site will automatically generate a framer.app domain.” You can pick a framer.website address, or connect your own domain on a paid site plan.
Its preview guide says: “Custom code added through Settings will not appear in the preview.” Its marketplace lists plugins such as Outseta and Thenty for member sign-in, gated content and Stripe payments.
Why keep your web app
As of October 30, 2026, we found no App Store or Google Play route in Framer's own publishing docs or plans, so you don't need to rebuild your site in another tool to be in the stores. BDK packages the site you already have: you keep designing and publishing in Framer, your CMS and your members stay where they are, and you get signed builds for both stores.
Be honest about what the app adds. A portfolio or a marketing site gives people little reason to install, and Apple's minimum-functionality guideline pushes back on apps that repackage a website. The Framer sites that make sense as apps are the ones people come back to: a member library, a course or publication with frequent releases, an event with a schedule and tickets, a directory people search. The native features are the reason to install: a push when something new is out, Face ID back into the member area, a ticket scanner at the door.
Your Framer site plan is a cost either way. As of October 30, 2026, Basic, the first plan with your own domain, is $10 a month billed yearly, and Pro, which adds Static Files, is $30 a month billed yearly. 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.
Moving the site itself off Framer is its own project. Framer's own help articles disagree on whether you can export a site to host elsewhere, so check before you plan on it.
What you need.
- Your site, published. A framer.app or framer.website 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 Framer project. BDK needs just 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 site's custom code, which Framer's help lists on paid plans.
$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 Framer site?
BDK Native turns your published Framer site into real iOS and Android apps for your own App Store and Google Play accounts. The apps load your live site, so you keep designing in Framer 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 Framer site into an iOS and Android app?
Publish it in Framer and give BDK the published address from the Publish panel: a framer.app or framer.website address, or your own domain, not a framer.com editor link. 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.
My site looks right in Framer's preview. Why test it on a phone?
Framer's preview is a resized website in your editor. Framer's own help notes menus that work in its preview but not on a phone, blur that renders differently once published, and custom code added in Settings that doesn't run in its preview at all. BDK Preview opens your published site on your own phone, as the app, with the phone features your code calls. What works there is strong evidence; it doesn't prove store review.
Will Apple accept my Framer site as an app?
Nobody can promise that: Apple and Google decide. Apple's minimum-functionality guideline pushes back on apps that add little beyond a website, and a portfolio or a landing page is the clearest case. Framer sites people come back to are a stronger fit: member libraries, courses and publications with frequent releases, events with schedules and tickets, directories people search. Give people a reason to install, like push when something new is out, Face ID back into their account or a ticket scanner. BDK's native features exist for that.
Will my changes in Framer show up in the app?
Yes. The app loads your live site, so whatever you publish from Framer, CMS items included, shows up in the installed apps right away, with no store update. Edits you haven't published yet, including on-page CMS edits waiting for review, show up once you publish. 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 Outseta, Thenty or FrameAuth sign-in work in the app?
Test it in BDK Preview before you buy: sign in, close the app, open it again, then log out and reset a password. Framer has no member sign-in of its own in its publishing docs, so the plugin you use decides how sessions work. Memberstack's docs list Framer among builders its standard setup doesn't support. 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 it in the phone's browser and returns to the app, called through the free @thebdk/native package. Whoever adds your site's code has to connect that to your sign-in plugin, so the member is signed in when they return. 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 members 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 Outseta or Thenty 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.
Last updated
See your own app on your phone, free, before you pay anything.