First, what a PWA actually is
A progressive web app is a web application that behaves like a native app: it installs to the home screen with its own icon, opens full-screen without browser chrome, works offline where it matters, and sends push notifications. It's built with web technology, which is where the cost advantage comes from — one codebase, no app-store gatekeeping, instant updates.
PWAs run on both Android and iPhone. On iOS they've been first-class citizens for a while now — including web push support since iOS 16.4 — with some platform limits we cover honestly below.
The cost difference in real numbers
In our published pricing: a PWA is £6,500 fixed (6–8 week build) and a cross-platform native app is £14,500 fixed (iOS + Android from one codebase, store submission included). Same team, same quality bar — the native route costs more because store packaging, review cycles and device-level testing are real work, not because of a margin. Both are on the pricing page.
For market context, industry surveys such as Business of Apps' cost research put typical native app builds anywhere from $30,000 to $300,000+ — ranges that reflect open-ended scope more than anything technical.
Side by side
| Progressive web app | Cross-platform native | |
|---|---|---|
| Our fixed price | £6,500 (~$8,000) | £14,500 (~$18,000) |
| Build time | 6–8 weeks | Longer, scoped per project |
| Installation | From a link — no store | App Store & Google Play |
| Updates | Instant, for every user | Store review, then user updates |
| Store costs | None | Apple $99/yr, Google $25 once; 15–30% commission on in-app digital sales |
| Push notifications | Yes (iOS 16.4+ on iPhone) | Yes, fully |
| Offline use | Yes, where designed in | Yes, fully |
| Deep device access | Limited (camera, location OK; background processing and some sensors restricted) | Full |
| Store discovery | No listing | Searchable in stores |
When native is worth the extra £8,000
We build both, so this isn't a sales pitch for either. Choose native (or cross-platform) when:
- You need deep hardware access — background location, Bluetooth peripherals, advanced camera control, HealthKit-style integrations.
- App-store presence is part of the plan — customers will search for you there, or a store listing signals credibility in your market.
- The app must do heavy work offline or in the background — syncing, tracking, processing while closed.
When a PWA is the smarter buy
- Customer portals and booking tools — users arrive from your website or an email link, not from store searches.
- Internal and field-team apps — no store friction; a link in the team chat and everyone's installed, updates land instantly.
- Validating an app idea — prove people use it before spending native money. A PWA is a real product, not a throwaway: if you later outgrow it, the backend, design and logic carry over to a native build.
- Content and commerce — and you keep 100% of sales, because web payments don't pay the 15–30% store commission on digital goods.
Questions we hear a lot
Can a PWA be listed in the app stores later?
Yes. Google Play accepts PWAs packaged as Trusted Web Activities, and a PWA can be wrapped for the Apple App Store. It's a common upgrade path: launch as a PWA, add a store presence when there's proof it's earning one.
Do PWAs really work properly on iPhone?
Yes, with honest caveats. Installation, offline use, full-screen mode and (since iOS 16.4) push notifications all work. Some capabilities remain restricted on iOS — background processing and certain sensors — which is exactly the conversation we have in scoping, before you spend anything.
Why is the native build more than double the price?
Store submission and review cycles, release management, device-matrix testing, and platform-specific behaviour all add genuine engineering time. We charge for the work that exists — and tell you when the cheaper route is the right one.