For Webflow sites
Put your Webflow site in the App Store and Google Play
BDK Native turns your published Webflow 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 Webflow 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 Webflow project, only your site's address.
Last updated
How it works with Webflow
Publish your site in Webflow.
Use the published address, like yoursite.webflow.io or your own domain. BDK needs that address, not a link from the Designer.
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 QR scanner, in-app purchases and push to one person start from the free @thebdk/native package, called from your site's custom code. Your backend or automation still sends one-person notifications and decides who has paid.
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, 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 I publish a new recipe in my Webflow CMS, send a push notification to everyone who has the app, and let readers send the recipe to a friend with the share sheet.
- Let members open their member area with Face ID instead of typing a password, and save their login so they skip the sign-in form next time.
- At the door of our event, let staff scan each ticket's QR code with the phone's camera, buzz the phone when the ticket is valid, and show the guest's name.
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 the moment a CMS item goes live needs an automation of your own. Memberstack or Outseta still handles sign-in, and your backend still checks each ticket.
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 site, published. A webflow.io 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 Webflow project or the Designer. 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 site's custom code.
What stays yours
- Your store listings, ratings and reviews. The apps are published from your own accounts.
- Your Webflow site, its CMS and your sign-in service.
- Your Webflow site and its CMS stay in Webflow. Your members and their accounts stay with the sign-in service you already use. 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.
Member sign-in
Webflow's own User Accounts were discontinued in January 2026, so your members sign in through a service like Memberstack or Outseta. Sign in, close the app and open it again, then log out and reset a password. 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 site's code calls it, and your sign-in service has to pick the session up when it returns. BDK Preview can show the hand-off, but it doesn't prove your store app's Google or Apple sign-in setup.
Shop and paid access
If you sell with Webflow Ecommerce, which runs on Webflow's own Ecommerce site plans, or with Stripe, walk through a real purchase, then a cancelled one, and check you land back in the app. 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.
Interactions, menus and forms
Scroll your heaviest pages, open the menu and fill in a form with the keyboard up, on both phones. The app shows your site as it is, so a page heavy with Interactions is just as heavy in the app. Accept and decline your cookie banner too, then close and reopen the app.
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. If a sign-in or other service asks you to host a file under /.well-known/ on your own domain, Webflow's pricing lists well-known files on its Premium site plan.
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 Webflow says
Webflow builds and hosts websites. Its Apps Marketplace lists integrations that extend your site and the Designer, not apps people install on their phones.
Webflow discontinued its own User Accounts on January 29, 2026, and points sites to sign-in services such as Memberstack and Outseta.
Why keep your web app
As of October 30, 2026, Webflow's plans don't include publishing to the App Store or Google Play, 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 Webflow, your CMS and your members stay where they are, and you get signed builds for both stores.
Your Webflow site plan is a cost either way. As of October 30, 2026, Basic is $15 a month billed annually or $25 monthly, and Premium, which adds the CMS, is $25 a month billed annually or $39 monthly. 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.
Compared with other app wrappers
One app on iOS and Android, with push notifications, for the first 12 months.
A wrapping subscription keeps charging. Natively's Unlimited plan, in the table, is $49 a month on monthly billing: its third charge brings you to $147, past BDK's one-time $99 for both platforms, and its second ($98) passes $69 for one platform. Its yearly plan, $384, passes either on the first payment.
| 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.
Moving off Webflow is a different step.
Pointing your app at a new address needs no new submission, but moving the site itself off Webflow is its own project, and Webflow's hosted CMS doesn't come along as a working CMS.
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 Webflow site into an iOS and Android app?
Publish it in Webflow and give BDK the published address: yoursite.webflow.io or your own domain, not a Designer 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.
Will my changes in Webflow show up in the app?
Yes. The app loads your live site, so whatever you publish from Webflow, new CMS items included, 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 my Memberstack or Outseta 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. Webflow's own User Accounts were discontinued in January 2026, so the sign-in your members use comes from a service like Memberstack or Outseta, and that service decides how long a session lasts. 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; your site's code 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.
Can I keep selling with Webflow Ecommerce in the app?
For physical goods and real-world services, including real-world subscriptions like a gym or a meal kit, yes: your Webflow 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.
Does my Webflow site need a custom domain?
Not to try it or to build it: BDK only needs a published address, and yoursite.webflow.io works. Webflow's paid site plans add your own domain. If you move to it later, point the app at the new address from your BDK dashboard, with no rebuild.
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 Webflow 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 scanner wired into what your site does. BDK's native features exist for that.
Docs
See your own app on your phone, free, before you pay anything.