Your customers are on their phones. You need an app-like experience but the thought of building separate iOS and Android apps — two codebases, two app store submissions, two maintenance bills — makes your finance director wince. Enter the progressive web app (PWA): a website with app superpowers. Installable, offline-capable, push notifications, full-screen — no app store required. It's not right for everything, but for a surprising number of UK businesses it's the smartest option nobody told them about.
What a PWA actually is
A PWA is a website built to modern standards that browsers can treat like an app. Users visit your URL, get prompted to "install" it, and from then on it lives on their home screen, launches full-screen without browser chrome, works offline (or with patchy signal — think warehouses, rural areas, the London Underground), and can send push notifications.
The technology behind it: service workers (scripts that cache content and enable offline use), a web app manifest (the metadata that makes it installable), and HTTPS throughout. No app store, no review queue, no 30% commission on anything, no forcing users through a 100MB download to check your opening times.
What PWAs do well
- One codebase, every device. Build once, run on iPhone, Android, desktop — anything with a modern browser. For businesses, this roughly halves development and maintenance cost versus native apps. Our app development clients are often surprised how far one codebase goes.
- Zero-friction adoption. No app store visit, no download, no permissions gauntlet, no "storage full" rejection. A customer goes from link to installed in seconds. For use cases where asking someone to download an app is a stretch — loyalty schemes, event apps, catalogues — this is transformative.
- Instant updates. Push a website update and every user has it immediately. No waiting for app store review, no users stuck on version 14 because they never update. For fast-moving businesses this alone is worth serious money.
- Offline resilience. Field teams, delivery drivers, engineers on sites with poor signal — PWAs keep working and sync when connectivity returns. Native apps do this too, but PWAs deliver it at web cost.
- Discoverable. It's still a website, so Google indexes it. Your "app" can rank in search and be linked to — two things native apps can't do.
Where PWAs fall short (the honest limits)
- iOS restrictions. Apple has historically limited what PWAs can do on iPhones — push notifications only arrived recently and with caveats, background sync is restricted, and some hardware APIs remain native-only. The gap is narrowing, but if your concept depends on deep iOS integration, check the current limitations carefully.
- No app store presence. For some categories, being in the App Store is the discovery channel. If your growth strategy depends on app store search and featuring, a PWA won't deliver that.
- Hardware-intensive features. Advanced camera processing, Bluetooth peripherals, AR, heavy gaming — the browser still can't match native for demanding hardware access. Our AR work, for instance, often needs native or WebAR-specific approaches.
- Platform feel. A well-built PWA feels close to native, but power users can tell. For consumer apps where polish is the product, native still wins.
PWA vs responsive site vs native app: the decision
- Responsive website is enough when: users visit occasionally, content is the product, and app-like features add little. Don't build a PWA for a brochure site.
- PWA wins when: repeat usage matters, offline capability helps, push notifications add value, you need cross-platform reach on a sane budget, or app-store friction would kill adoption. Loyalty programmes, B2B portals, field tools, event apps, content platforms — classic PWA territory.
- Native app wins when: you need deep hardware access, app store discovery is core to growth, or the experience demands pixel-perfect platform polish. Also when your audience simply expects "an app" — consumer finance, fitness, social.
There's also a pragmatic middle path many UK businesses take: launch as a PWA to validate the concept and build the audience, then go native for the platforms where the data justifies it. You've de-risked the investment and you know exactly what the native app needs to do.
What a good PWA needs (beyond the tech)
The technology is the easy part. What separates PWAs people keep from ones they delete:
- A reason to install. Offline access, faster repeat use, notifications they'll actually want — give users a payoff for the home-screen slot.
- Thoughtful notifications. Push is a privilege. Useful, timely, infrequent — or users revoke it and you've lost the channel. Plan the notification strategy before you build.
- Genuine offline value. Don't just cache the shell — design what the app does without connectivity. A field-service PWA that can't show today's jobs offline has missed the point.
- Performance obsession. PWAs live or die on speed. Every kilobyte matters on patchy mobile connections; performance budgets aren't optional.
Real-world PWA use cases in the UK
Where PWAs are quietly winning with British businesses right now:
- Field service and trades. Engineers accessing job sheets, manuals and customer history on sites with unreliable signal — offline-first PWAs that sync when connectivity returns. One codebase covering the whole team's mix of Android and iPhone devices.
- Hospitality ordering. Pubs and restaurants with table ordering via QR code — no app download between the customer and their pint. The zero-friction argument at its strongest.
- Retail loyalty. "Add to home screen" loyalty schemes that customers actually adopt, because there's no 80MB download and no account-creation gauntlet. Push notifications for offers, offline access to the loyalty card.
- B2B customer portals. Order history, reordering, invoices, support — the portal clients use weekly. Discoverable via search, installable for regulars, updated instantly when you ship improvements.
- Event and venue apps. Schedules, maps, live updates for festivals, conferences and attractions — needed for three days, not worth a download. The PWA's disposability is the feature.
The pattern: repeat usage, poor connectivity, mixed devices, or adoption friction that would kill a native app's business case. If two or more apply to your situation, a PWA deserves serious consideration.
We build progressive web apps and native apps for UK businesses — and we'll tell you honestly which one your project needs (sometimes the answer is neither). If you're weighing the options, our Flutter vs native guide covers the cross-platform question from the native side. Get a free consultation.
