For Webflow sites

Put your Webflow 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 Webflow. Pay once when it's right.

See pricing
  • 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 Webflow 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.

What each free preview lets you test on a phone
BDK PreviewNatively PreviewMedianDespiaMobiLoud
Push notificationsYes¹YesNo 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.
CameraYes²No
Record and play audioYes²No
Deep linksYes³No
In-app purchasesSample products⁴No
Face ID / fingerprintYes²Not documented
Google / Apple sign-inShows the hand-off⁵No (social login)
Your own loading screenYes⁶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.

  1. Push in BDK Preview runs on BDK's own keys; your own OneSignal and Firebase keys are used in your build.
  2. Phone features that need no account of your own run in Preview, as they will in your build.
  3. Deep links in Preview run through BDK's Branch / ChottuLink setup, under BDK's branding.
  4. Purchases in Preview use BDK's sample products; your own products work in your own build.
  5. BDK Preview can show the hand-off, but it doesn't prove your store app's Google or Apple sign-in setup.
  6. Your loading screen, in Preview. Your own icon shows in your build.
  7. 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

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.

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 November 5, 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 Webflow.

  1. Publish your site in Webflow.

    Use the published address, like yoursite.webflow.io or your own domain, not a link from the Designer.

  2. Open it on your phone.

    Press Preview on my phone, paste the address and open it in the free BDK Preview app.

  3. 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. Your backend or automation still sends one-person notifications and decides who has paid.

  4. 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 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.

Before you buy.

Check these on your phone first.
  • 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 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.

What Webflow says about app stores. Webflow builds and hosts websites; its plans don't publish to the stores.

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.

Moving the site itself off Webflow is its own project, and Webflow's hosted CMS doesn't come along as a working CMS.

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.
  • 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 Webflow project or the Designer. 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.

$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 Webflow site?

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.

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 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 needs just 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 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 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.

Last updated

See your own app on your phone, free, before you pay anything.

See pricing