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 Squarespace sites
Put your Squarespace 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 Squarespace. 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 Squarespace login private. BDK needs just your site's public 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 Squarespace.
Make your site public in Squarespace.
Use the public address, like yoursite.squarespace.com or your own domain, never a /config editor link. A site that is still private or on a trial isn't ready.
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, the share sheet and in-app purchases start from the free @thebdk/native package, added through Code Injection. Squarespace offers Code Injection on Core and above, not Basic. Squarespace still decides who has paid. A scanner at the door works when your site, rather than the QR code alone, can say that this person booked or 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 Code Injection, 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 post a new lesson in my member area, send a push notification to everyone who has the app, and let members listen to the lesson with the phone's own audio player, even with the screen locked.
When a product someone bought last month is back in stock, send them a push notification, and open that product in the app when they tap it.
When a shopper taps Share on a product, open the phone's share sheet so they can send it to a friend or post it to their Instagram story, and give a short buzz when they add something to the cart.
These start from the free @thebdk/native package, added through Code Injection on Core or above. You can send a push by hand from OneSignal; sending one the moment a lesson goes live needs an automation of your own. Audio that keeps playing with the screen locked is chosen when you order the build. Checking a pass at the door still needs your backend: a QR code alone doesn't prove anyone has booked or paid.
Before you buy.
Check these on your phone first.
Customer accounts and member pages
Sign in with a customer account the way your customers do, then close the app and open it again. Open a member page as a member and as someone who isn't one, and reset a password. Do it logged out of your owner account. If your site offers Google sign-in, Google doesn't allow its sign-in page inside an app's embedded browser, so it has to open in the phone's browser and come back. BDK's external sign-in opens it in the phone's browser, called from your site's code through the free @thebdk/native package. Whoever builds your site, or your AI, then has to connect the return to your site's login, so check that customers arrive back in the app signed in. BDK Preview can show the hand-off, but it doesn't prove your store app's Google or Apple sign-in setup.
Checkout and paid access
Walk through a real order with Squarespace Payments, Stripe or PayPal, then a cancelled one, and check the cart and your sign-in survive closing the app. Squarespace's checkout pages don't take code, so checkout stays Squarespace's own. 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. A paid member area of lessons or videos can count as digital, so check the stores' rules first. BDK's in-app purchase helpers start those flows from your other pages; you set up the products, and your backend decides who has paid. An in-app purchase doesn't unlock a Squarespace member area by itself: connecting the two is yours to build. In BDK Preview, purchases run against BDK's own sample products; your own products work in your own build.
Forms, uploads and bookings
Fill in a form with the keyboard up, upload a file and book something, on both phones. Do it logged out: Squarespace's docs say form redirects don't work while you're logged in to the site. File upload fields use reCAPTCHA, so check that it shows and passes inside the app.
Your address
If your site has its own domain, give BDK that primary domain, not the squarespace.com address: Squarespace's built-in address doesn't redirect to your primary domain, so sign-ins and carts can differ between the two. Open the app logged out and check it lands on your real home page.
Links from your emails
Tap an order email or a password-reset link 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 service asks you to host a file under /.well-known/ on your domain, check it works first: people on Squarespace's forum report trouble serving those files.
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 Squarespace says about apps. The Squarespace app is for editing your site, not for publishing an app of your own.
What Squarespace says
Squarespace builds and hosts websites that adapt to phones. Its guide describes the Squarespace app, on iOS and Android, as a way to “edit your site from a mobile device.” Mobile Start is a 30-day website plan bought by in-app purchase in the iOS app.
Code Injection adds scripts to your site's header or footer. Squarespace lists it as a premium feature on Core, Plus and Advanced, not Basic, and its docs say: “Checkout pages don't support code.”
Its Device view gives a “general idea” of how your pages look on a phone, and Squarespace says it's “not 100% accurate for every phone or tablet.”
Why keep your web app
As of October 30, 2026, Squarespace's plans don't include publishing your site as an app in the App Store or Google Play, and the Squarespace app is for editing your site. 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 editing in Squarespace, your shop, members and bookings stay where they are, and you get signed builds for both stores.
Not every Squarespace site should be an app. Apple's guidelines push back on apps that add nothing beyond a website, so a brochure, a portfolio or a page with your menu and address makes a weak app. The sites that fit are the ones people come back to: a shop they reorder from, classes or events they book, a member area with new lessons, or news you post often. Make native features the reason to install: a push when a new lesson goes live, a pass scanner at the door, Face ID, the share sheet.
Your Squarespace plan is a cost either way. As of October 30, 2026, in US dollars, Basic is $19 a month billed annually or $25 monthly, and Core, the first plan with Code Injection for the free @thebdk/native package, is $29 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 Squarespace is its own project, because Squarespace hosts your pages, your shop and your member areas.
What you need.
- Your site, public, on a paid Squarespace plan. A squarespace.com 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 Squarespace account or the editor. 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, added through Code Injection on Core, Plus or Advanced.
$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 Squarespace site?
BDK Native turns your published Squarespace 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 editing in Squarespace and every change to your live site 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 Squarespace site into an iOS and Android app?
Make your site public in Squarespace and give BDK its public address: yoursite.squarespace.com or your own domain, never a /config 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. After that, whatever you change on your live site 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.
Isn't the Squarespace app the same thing?
No. The Squarespace app is for you, the owner: Squarespace's guide says it lets you edit your site from a mobile device. It doesn't give your site its own listing in the App Store or Google Play, and Mobile Start, bought in the iPhone app, is a plan for your website. BDK builds and signs iOS and Android apps from your live site, and you submit them from your own developer accounts. Keep using the Squarespace app to edit; your changes show up in your app too.
Which Squarespace plan do I need?
BDK needs just your public address, so the app itself works with any paid plan that keeps your site public, and push to everyone needs no code. For other phone features you add the free @thebdk/native package through Code Injection, which Squarespace lists as a premium feature on Core, Plus and Advanced. Its docs say JavaScript stops working if you move down to Basic, and checkout pages don't take code on any plan.
Will my customer accounts and member areas work in the app?
Test them in BDK Preview before you buy: sign in with a customer account, close the app, open it again, then open a member page and reset a password, logged out of your owner account. Squarespace's own customer accounts use an email and password on your site's pages, so that is the first thing to check. If your site offers Google sign-in, Google doesn't allow its sign-in page inside an app's embedded browser, so it has to open in the phone's browser and return to the app. BDK's external sign-in opens it there, called from your site's code through the free @thebdk/native package. Whoever builds your site, or your AI, then has to connect the return to your site's login; test that customers arrive back in the app signed in. 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 my Squarespace checkout in the app?
For physical goods and real-world services, including real-world subscriptions like a gym or a meal kit, yes: your Squarespace checkout, with Squarespace Payments, Stripe or PayPal, 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. A paid member area of lessons or videos can count as digital, so check the stores' rules before you sell it in the app. BDK's in-app purchase helpers start those flows from your own pages, not from checkout, which takes no code; you create the products in App Store Connect and Google Play Console, and your backend decides who has paid. An in-app purchase doesn't unlock a Squarespace member area by itself. 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 my Squarespace site as an app?
Nobody can promise that: Apple and Google decide. Apple's guidelines push back on apps that add nothing beyond a website, so a brochure or portfolio site makes a weak app. Squarespace sites people come back to fit better: a shop they reorder from, classes they book, a member area with new lessons, or news you post often. Give people a reason to install, like push notifications for new lessons, a pass scanner at the door or Face ID. BDK's native features exist for that.
Last updated
See your own app on your phone, free, before you pay anything.