Squarespace PWA vs native app: which one should you build?

Updated September 2026

What a PWA actually is — and what Squarespace does to it

A Progressive Web App is a website plus three things: a manifest that gives it a name and an icon, a service worker that lets it cache and receive messages, and a set of icons and splash screens. Add those and the browser will offer to "install" the site — after which it opens in its own window, without browser chrome, with your icon on the Home Screen. It is a genuinely good piece of technology and for a lot of sites it is the proportionate answer.

On Squarespace there is one mechanical wrinkle worth understanding before you buy anything, from anyone. A service worker — the piece of a PWA that delivers push and makes the site installable — cannot be added to a Squarespace site. Progressier, the PWA toolkit in the Squarespace Extensions marketplace, says so plainly in its own Squarespace documentation: "Unfortunately, Squarespace does not support adding a service worker to your domain."

The practical consequence is that the installable app is served from the tool's own hosted installation page — an address of the form install.page/<your-slug> — rather than from your domain. That is a Squarespace platform constraint, not a vendor shortcoming: it applies to any PWA tool on Squarespace, and their answer to it is a reasonable one. It does mean the thing you send people to install is not on your own domain.

Progressier is a real option and it is good at what it does. If you are weighing it, these are its genuine advantages, and none of them have an asterisk:

• It is live in minutes. No review queue, no rejection, no waiting.
• No developer accounts. Nothing to register with Apple or Google, ever.
• A fixed, predictable price. You know your bill in advance — that is a real thing to buy.
• It installs on desktop too. Mac and PC, not just phones. No store app can do that from a website.
• Updates are instant. It is the website, so when the site changes the app has already changed. There is no release cycle and nothing to resubmit.
• Install surfaces that live on your own site — an install button, a banner, a floating app icon, a QR code — so you can prompt people where they already are.

They are also honest about where a PWA pays off. Their own guidance is that the conversion "generally benefits specific sites, like e-commerce platforms and certain blogs", while "portfolio websites and promotional landing pages might not gain much". That is a fair thing for a vendor to say about their own product, and it is worth reading twice before you buy anything — including from us.

The iPhone question — the one that usually decides it

If push notifications are why you want an app, this section is the whole decision.

Web push on iPhone works only inside an installed PWA — Apple's own platform requirement since iOS 16.4. "Installed" on an iPhone means the visitor did this, by hand:

1. Opened your site in Safari — not Chrome, not an in-app browser, Safari.
2. Tapped the Share button.
3. Scrolled the share sheet.
4. Tapped Add to Home Screen.
5. Confirmed.
6. Opened the new icon.
7. Accepted the notification prompt.

Seven steps, none of which iOS offers to do for them, before your first notification can be sent. A tool can put an install banner or a floating icon on your site to start that flow — they ship all of those — but it cannot remove the share-sheet step, because the platform owns it.

A store app has a different shape: search, Get, open, accept the prompt the operating system itself raises. The install is the thing iPhone users already do a dozen times a year, and the notification permission dialog is one they recognise.

That is the honest asymmetry. On the platform where most Squarespace shoppers are, a PWA charges every single push subscriber a manual, multi-step install, and a store app does not. If you do not need push, this section costs you nothing — skip it and read "Choose a PWA if…" below.

PWA, webview wrapper, native app — side by side

Three different things get called "turning your website into an app". They are not variations of each other; they are different artifacts with different costs.

* Quoted from Progressier's own published documentation, checked 17 September 2026. The webview-wrapper column describes the category, not any one vendor.

Choose a PWA if…

• You need it live today. A store timeline does not work for you, and a PWA has none.
• You never want to think about app releases. The site is the app; changing one changes the other.
• Desktop matters. You want people installing it on a Mac or a PC, which no store app does from a website.
• You do not want a store presence at all — no developer accounts, no review, no rejections, no annual renewal.
• A predictable bill is part of what you are buying. Flat pricing is genuinely easier to plan around than metered pricing, ours included.
• Your site is a brochure, a portfolio or a landing page and you mainly want an icon on the Home Screen. Worth knowing that their own guidance says such sites "might not gain much" from a PWA — but if you want an app presence anyway, this is the proportionate way to get one, and a native app would be a lot of work for the same outcome.

If you read that list and nodded, stop here and go get a PWA. That is a real recommendation, not a setup for a counter-argument.

Choose a native app if…

• You want to be found. People search the App Store and Google Play the way they search Google. A PWA is in neither — their own documentation says "it's not possible to make it available through Google Play or the App Store as a PWA".
• Push on iPhone is the point. You need to reach iPhone customers without each of them completing a seven-step manual install first.
• You need to know who your customer is. Accounts, segments, and messages aimed at one person rather than everyone — the two capabilities their own documentation says are not possible on Squarespace.
• The app has to be yours. Your listing, your icon, your brand, your reviews — not a shared install page on someone else's domain.
• Your app has to do something the website does not. Native screens, device features, content that works without a connection.
• You are building this for clients. PWA tooling is generally licensed per app, so five client sites means five apps and a bigger tier; Choicely meters work rather than app count.

What a native app costs that a PWA does not

Anyone comparing these two who does not tell you this is not being straight with you:

• Apple charges $99 a year for the Apple Developer Program. It is a subscription, and it is required for as long as your app is in the App Store.
• Google charges a one-time $25 registration fee for a Google Play developer account.
• App review takes time. Both stores review every submission, and both can reject one. Plan for it. How long app review takes and why apps get rejected are the honest versions of both.

Choicely does not mark either fee up — you pay Apple and Google directly. A PWA has none of these costs, no review and no rejection risk, which is a real advantage and the main reason the PWA route exists.

On our side: our free plan includes push notifications, unlimited collaborators and the publishing service, so you can build and see the app before you decide anything. Plans are metered by work rather than by app count, so building a second app does not move you up a tier. Flat, per-app pricing is the more predictable model of the two; ours is the one that does not punish you for having more than one app. Which of those you prefer is a real preference — the numbers for ours are on /pricing, which is the only page we keep them on, because a stale price is worse than none.

What Choicely builds from a Squarespace site

Paste your Squarespace URL into Choicely Studio and it reads your site — pages, posts, galleries, images and brand — and builds native iOS and Android screens from it. You refine it in chat rather than in a template picker: feature a section, change the home screen, add a video block. Publish Assistant then takes it to the App Store and Google Play, and Image Studio generates the store screenshot kit both stores demand.

Your Squarespace site keeps running exactly as it does now. The app is a second surface, not a migration, and content changes in Studio do not need a new store submission. Once it is live, push and engagement are where a store app earns its keep.

What is not there yet, said plainly: commerce is the active gap — imported products currently arrive without a purchase path, and that work is in progress. If your app has to sell today, wait for it or talk to us first. We would rather say that here than have you find it after you have built the app.

Sources and disclosure

• Every quoted PWA limitation — Progressier's own Squarespace documentation, checked 17 September 2026.
• Their PWA-fit guidance ("generally benefits specific sites, like e-commerce platforms and certain blogs"; "portfolio websites and promotional landing pages might not gain much") — same source, same date.
• Their advantages above — their published feature and pricing pages, same date.
• Apple Developer Program and Google Play fees — what it costs to publish an app, kept current.
• Choicely capabilities — /pricing and /publish-app.

Choicely builds native mobile apps, so we have a stake in this comparison. We have tried to make the case for the other side as well as the case for ours; every limitation we attribute to a PWA is quoted from the vendor's own published documentation on the date shown, and vendors change their products without notice.

See your Squarespace site as a real app

Paste your Squarespace URL and watch Choicely build native iOS and Android screens from your own content. Free to start, push notifications included, and you decide about the App Store afterwards. Related: website to app converter · publishing service · how to publish to the App Store · pricing.