- 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 Softr apps
Try a sample purchase, the camera, a deep link, Face ID and push on your own phone, free, while you build in Softr. Pay once when it's right.
Sample products in Preview. Your own products in your build.
All five run in the free BDK Preview app.
Keep your Softr workspace and data private. BDK needs just your app's address. On iPhone, BDK Preview opens your own previews.
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.
| 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.
Like buying a bike instead of renting one every month. BDK is one payment; a wrapper subscription keeps charging.
One payment
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.
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
Published from your own Apple and Google accounts. Ratings, reviews and installs are yours.
It comes with every Android build.
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.
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
Use the published address: the softr.io address Softr gave you, or your own domain. BDK needs that address, not a link from the Softr editor.
Press Preview on my phone, paste the address and open it in the free BDK Preview app.
Push to everyone needs no code: you send it from your own OneSignal account. Face ID, the QR scanner, the camera and push to one person start from the free @thebdk/native package. You add it with a Custom Code Block, which Softr's docs list on Pro and above.
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.
Tell your AI, or whoever adds your Custom Code Blocks, 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 job is assigned, notify that technician. Show their open-job count on the iPhone app icon, and use notification badges on Android.
Let customers open their portal with Face ID instead of typing a password, and save their login so they skip the sign-in form next time.
Let our team scan the QR code on a machine to open its maintenance record, and take a photo of the repair with the phone's camera.
These start from the free @thebdk/native package in a Custom Code Block. Your own automation still decides who gets each notification and remembers which phone belongs to which user; Softr still handles sign-in and who can see each record. On iPhone the badge can be a number; on Android it follows the notification. Saving the photo onto the record stays in Softr. Face ID and saved login need an integration with your existing sign-in system. Check that this works with your Softr setup before relying on it.
Softr can sign people in with a magic link, an emailed code or a password. A magic link tapped in the phone's mail app may open in the phone's browser instead of your app, so try every way your users sign in, then close the app and open it again. A code or password typed on the page inside the app is worth trying too: it does not send them out to the mail app. Close the app, open it again, and check that they are still signed in.
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 to the app. BDK's external sign-in does that hand-off, called from your code; check that your Softr session comes back with it rather than assuming it does. BDK Preview can show the hand-off, but it doesn't prove your store app's Google or Apple sign-in setup.
If you charge with Softr's Stripe checkout, walk through a real purchase and the customer portal, 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 automation decides who has paid. In BDK Preview, purchases run against BDK's own sample products; your own products work in your own build.
The app opens your Softr app, so your Softr plan still applies, user limits included. Softr's paid plans include a custom domain; its Free plan doesn't. Sign in as each kind of user you have and check what each one can see.
Try sample push in BDK Preview. After receiving your own build, test notifications from your OneSignal account. Test Softr's workflow notifications separately in its installed web app.
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.
Softr's FAQ says: “Softr builds are PWAs (progressive web apps) and cannot be published to the iOS App Store or Google Play.” It adds that this applies across all plans.
Its mobile app is installed from the browser to the home screen and needs an internet connection. Softr's FAQ still says Professional plan users and above. Professional is an older plan name, not the current plan called Pro. A recent Softr post lists the installable app on the Business plan. Check which applies to your subscription.
Softr workflows can send push notifications to the installed web app or to an in-app inbox, on Business and above.
Softr's mobile app is an installable web app, not an App Store or Google Play listing. BDK builds and signs iOS and Android apps from your live Softr app. You submit them from your own developer accounts; Apple and Google decide whether to approve them. You don't need Softr's installable app for this: the store app opens your live Softr app.
Your Softr plan is a cost either way. As of October 30, 2026, Basic, the first paid plan and the first with a custom domain, is $19 a month billed annually or $25 monthly, and Pro, the first plan where Softr's docs list the Custom Code Block, is $99 a month billed annually or $119 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 app itself off Softr means rebuilding it somewhere else: Softr hosts the blocks your app is made of.
$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
BDK Native turns your published Softr app into real iOS and Android apps for your own App Store and Google Play accounts. The apps load your live Softr app, so you keep building in Softr 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.
Publish it in Softr and give BDK the published address: the softr.io address Softr gave you or your own domain. 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.
No. Softr's mobile app is an installable web app: people add it to their home screen from the browser, and Softr's FAQ says it can't be published to the App Store or Google Play on any plan. BDK builds and signs iOS and Android apps from your live Softr app. You submit them from your own developer accounts; Apple and Google decide whether to approve them. You can keep both.
Yes. The app loads your live Softr app, so whatever you publish from Softr 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.
Test them in BDK Preview before you buy. A magic link tapped in the phone's mail app may open in the phone's browser rather than in your app, so the user ends up signed in there instead. A code or password typed on the page inside the app is worth trying too: it does not send them out to the mail app. Close the app, open it again, and check that they are still signed in. 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 to the app. BDK's external sign-in does that hand-off, called from your code through the free @thebdk/native package; check that your Softr session comes back with it rather than assuming it does. BDK Preview can show the hand-off, but it doesn't prove your store app's Google or Apple sign-in setup.
For physical goods and real-world services, including real-world subscriptions like a gym or a meal kit, yes: your Softr 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 or automation decides who has paid. In BDK Preview, purchases run against BDK's own sample products; your own products work in your own build.
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.
BDK needs just your published address, so the app itself doesn't need a particular Softr plan, and your plan's user limits still apply. Softr's paid plans include a custom domain; its Free plan doesn't. For phone features beyond push to everyone, you add the free @thebdk/native package with a Custom Code Block, which Softr's docs list on Pro and above.
Last updated
See your own app on your phone, free, before you pay anything.