If you run a café on Square and want customers ordering from their phones, you’ll hit this fork quickly: build a PWA (a progressive web app — essentially a website that behaves like an app) or ship a native app to the Apple App Store and Google Play. The two get pitched as interchangeable. They aren’t. They differ most on the exact things that decide whether mobile ordering actually grows repeat business: a home-screen icon, store discoverability, and push notifications that reliably land.
This is the honest comparison — what each is, what each costs, where each wins, and how to choose for a small café or restaurant.
What is a PWA?
A PWA is a website built with modern web features so it can act like an app. Customers visit a URL, and on a supported browser they can tap “Add to Home Screen.” After that, it opens full-screen with its own icon, works offline for cached content, and can — with caveats — send push notifications.
The appeal is real: one codebase serves every device, there’s no app-store review to pass, and you can ship updates instantly without waiting for Apple or Google to approve them. For a café that just wants a fast, no-download ordering page, a PWA (or even a plain Square Online site) is a legitimate, low-friction option.
What is a native app?
A native app is a separate program built for iOS and Android and distributed through the Apple App Store and Google Play. The customer searches, taps “Get,” and the app installs with a permanent icon on their home screen. Native apps get first-class access to the operating system: reliable push through Apple’s APNs and Android’s FCM, Apple Pay and Google Pay, the camera, and a smoother, more app-like feel.
The cost is more process. You need an Apple Developer Program membership at $99/year and a one-time $25 Google Play registration, and every release goes through store review. That’s exactly why most independent cafés don’t build a native app themselves — they use a platform that ships a branded one for them.
The honest side-by-side
| Factor | PWA | Native app |
|---|---|---|
| Where customers get it | A URL + “Add to Home Screen” | App Store + Google Play |
| App-store presence | None | Yes — searchable, reviewable |
| Home-screen icon | Only if manually added | By default after install |
| Push notifications | Works, but less reliable; iOS needs home-screen install | Reliable, OS-level (APNs / FCM) |
| Apple Pay / Google Pay | Supported on web, with limits | Full native support |
| Upfront cost | Lowest; no store fees | Apple $99/yr + Google $25 once |
| Updates | Instant, no review | Through store review |
| Discoverability | Search engines only | App stores + search |
| Best for | Fast, no-download ordering | Repeat business, loyalty, push |
Store fees: Apple Developer Program and Google Play developer pricing, 2026. Confirm current rates before you decide.
Where the PWA falls short: push and presence
For a café, the entire point of getting onto a customer’s phone is bringing them back — and the two levers for that are a visible home-screen icon and a notification you can send when you choose. PWAs are weakest exactly here.
Push notifications on iPhone are conditional. Apple only enabled web push for PWAs in iOS 16.4 (2023), and only when the customer has manually added the PWA to their home screen through Safari’s Share menu. An open browser tab does not count. In practice this multi-step install requirement means the audience you can actually reach with PWA push is a fraction of what a native app reaches, and developers widely report that PWA push subscriptions can silently disappear. Native push, by contrast, runs through the operating system and is far more dependable.
The home-screen icon is opt-in. A native app puts its icon on the phone the moment it installs. A PWA only earns that icon if the customer knows to tap “Add to Home Screen” — a step most people never take. No icon means your café isn’t a glanceable tap away; it’s a URL they have to remember.
There’s no app-store listing. A storefront in the App Store and Google Play is its own form of credibility and discovery. A PWA lives only at a web address. None of this makes a PWA useless — it makes it a better web ordering page than a retention channel.
Where the native app costs more
Fairness goes both ways. A native app is more to stand up:
- Two builds and two stores. iOS and Android are different platforms with different review processes, plus the Apple and Google developer accounts and their fees.
- Store review and rejections. Apple’s guidelines (notably 4.3, aimed at low-effort or template apps) reject thin restaurant apps, so the app has to clear a real bar.
- Update lag. A change ships only after store review, not instantly like a website.
For a single café, building and maintaining a native app from scratch is rarely worth it — which is the real reason this debate exists. The practical answer for most isn’t “DIY PWA vs. custom native build.” It’s a done-for-you branded native app that handles the stores, the review, and the updates for you on a flat monthly fee.
A decision model for a café
Run these questions in order:
1. Do you just need to take orders, or do you need to bring people back? If you only need a no-download ordering page, a PWA or a free Square Online site versus a branded app is enough. If repeat visits are the goal, you need reliable push and a home-screen icon — that points to native.
2. How much does push notification reliability matter to you? If you plan to send “your order’s ready,” slow-afternoon offers, or a Friday reminder, native push lands far more dependably than PWA push, especially on iPhone. Weak push undercuts the whole reason to be on the phone. See how cafés use push for retention for what that looks like in practice.
3. Do you want to be findable in the App Store? A store listing is discovery and credibility a PWA can’t match. If you want customers (and your staff) to search “[your café] app” and find you, that’s native.
4. Who’s building and maintaining it? If the honest answer is “not me,” a DIY PWA still needs upkeep, and a custom native build needs a developer. A managed branded-app platform removes that entirely — which usually makes the cost question moot.
A cost comparison (illustrative)
To make the trade-off concrete — these figures are illustrative, not quotes:
- DIY PWA: low or no upfront build if you’re technical, no store fees, but it’s your ongoing maintenance, and you inherit the weaker push and missing store presence.
- Custom native app: a one-time build that can run well into five figures for iOS + Android, plus Apple’s $99/year and Google’s $25, plus ongoing maintenance and store-review cycles every update.
- Managed branded native app: a flat monthly platform fee that bundles the iOS and Android apps, store submission, updates, loyalty, and push — no separate developer, no per-update review headache for you.
For an independent café, the managed route usually wins because it delivers the native-only advantages — store presence, home-screen icon, reliable push — without the custom-build price tag. That’s the niche Tany fills: a branded iOS and Android ordering app built on your existing Square POS, live in about a day for $99 CAD/month per location, with loyalty, eGift cards, and push included. It’s one worked example of the “native without the overhead” option — the broader point stands on its own.
So which should you choose?
If mobile ordering is a convenience feature and nothing more, a PWA or a free web ordering page is a perfectly honest answer — cheap, fast, no app stores. If mobile ordering is meant to drive repeat visits, the home-screen icon, store presence, and reliable push of a native app are worth it, and a managed branded app gets you there without a custom build.
The mistake is choosing a PWA because it’s cheaper and then expecting it to do a native app’s retention job. Match the tool to the goal: web page for convenience, native app for loyalty. If you’re weighing it against simply turning on Square’s own tools first, our Square Online vs. branded app guide lays out that starting step.