Native mobile apps used to be the only credible option if you wanted a serious mobile presence. Build for iOS, build for Android, get approval from Apple and Google, then convince customers to download yet another app. The cost: £50,000-£200,000. The reality: most apps are downloaded once and abandoned within a week.
Progressive Web Apps (PWAs) changed the maths. They install straight from the browser, work offline, look and feel like native apps, and cost a fraction of native development. Brands like Starbucks, Pinterest, Trivago and Forbes have rebuilt their mobile experiences as PWAs and reported conversion uplifts of 50-200%.
For UK SMEs, PWAs are often the right answer for adding mobile capability without the native app investment.
What Is a Progressive Web App?
A PWA is a website built with modern web technologies that behaves like a native app. Specifically, it can:
- Install on a user's home screen (no App Store required).
- Work offline with cached content.
- Send push notifications (with permission).
- Access device features like camera, location and notifications.
- Load instantly thanks to service workers and aggressive caching.
- Run full-screen without browser chrome.
Behind the scenes, a PWA is just a website with three additional ingredients: a web app manifest (tells the browser how to install it), service workers (handle offline and caching), and HTTPS (required for security).
Why PWAs Matter Now
Two trends made PWAs essential rather than optional in 2026:
iOS finally caught up. Until iOS 16.4, PWAs on Apple devices were second-class citizens. Apple now supports push notifications, badging and full installability. The last technical excuse to build native is gone for most use cases.
Mobile traffic dominates. 60%+ of UK web traffic is mobile (Statista 2025). If your mobile experience is slow or clunky, you're losing the majority of potential customers before they convert.
App store fatigue is real. UK consumers download an average of 3-4 new apps per year. Most app downloads are friction. PWAs eliminate that friction completely. "Add to home screen" takes 3 seconds and 0 storage commitment.
PWA vs Native App vs Website
Native app: Best for graphics-heavy games, AR/VR, deep device integration (HealthKit, ARKit), or businesses with budget for two separate codebases. Costs £50,000-£200,000+ to build, plus ongoing platform fees and approval delays.
PWA: Best for content sites, ecommerce, booking systems, productivity tools, news, services. Costs £5,000-£30,000 to build, no app store fees, instant updates without re-approval.
Standard website: Best if mobile experience doesn't need to feel app-like and you don't need offline or push notifications. Lowest cost, simplest stack.
For most UK SMEs, the choice is PWA vs standard website. Native is usually overkill.
Real PWA Examples (and the Numbers)
- Starbucks PWA: 2x daily active users vs the native app. Same features, lower friction.
- Pinterest PWA: 60% increase in core engagement, 44% increase in user-generated ad revenue.
- Trivago PWA: 150% increase in re-engagement, 97% increase in click-outs to hotel offers.
- Forbes PWA: 2x sessions per user, 100% increase in scroll depth.
- AliExpress PWA: 104% conversion rate increase across all browsers.
The pattern: PWAs consistently outperform both native apps (because they don't require download) and traditional mobile sites (because they feel native).
When PWAs Make Sense for Your UK Business
Strong fit: - Ecommerce stores wanting a faster mobile checkout experience. - Booking and reservation platforms (restaurants, salons, gyms). - News and content publishers with frequent return visitors. - SaaS dashboards used regularly by the same users. - Service businesses with repeat customer interactions. - Membership and community platforms.
Weaker fit: - One-off transactional sites where users won't return. - Heavy graphics or 3D experiences. - Businesses needing deep iOS-specific features. - Apps where App Store visibility is itself a marketing channel.
If 30%+ of your users return within a month, a PWA usually pays back inside a year through engagement and conversion improvements.
How to Build a PWA
Technical Foundations
- HTTPS: Required.
- Web App Manifest: A JSON file describing your app (name, icons, theme colours, display mode).
- Service Worker: JavaScript that runs in the background, handling caching and offline.
- Responsive design: Must look brilliant on every screen size.
Tech Stack Options
- Next.js: Excellent PWA support out of the box with next-pwa plugin. Our preferred stack for client PWAs.
- Vue/Nuxt: Strong PWA tooling, popular in European agencies.
- Vanilla HTML/JS: Possible but more work for anything non-trivial.
- WordPress with PWA plugin: Functional but performance is limited by WordPress's general overhead.
For a deeper comparison of stack choices, see our headless CMS guide.
What to Test Before Launch
- Lighthouse PWA score (aim for 90+).
- Install prompt behaviour on iOS and Android.
- Offline functionality.
- Push notification flow (with permission).
- Add-to-home-screen experience.
- Performance metrics (Core Web Vitals).
Cost and Time
- Building a PWA from scratch: £5,000-£30,000 depending on complexity. Most marketing PWAs sit in the £8,000-£15,000 range.
- Adding PWA features to an existing modern site: £2,000-£6,000 if your site is already built on Next.js, Vue or similar.
- Adding PWA to WordPress: £1,500-£4,000 for plugin setup and customisation.
- Native app equivalent: 5-10x the cost. Typically £50,000-£200,000+.
The break-even maths is usually clear within months for businesses with regular mobile traffic.
Common PWA Mistakes
- Forgetting offline. A PWA without proper offline handling is just a slow website.
- Bad push notification UX. Asking for permission immediately on landing kills conversions. Wait for engagement signals.
- Ignoring iOS edge cases. iOS PWA behaviour still differs from Android. Test thoroughly.
- Not promoting installation. Most users don't realise they can install your PWA. Add a contextual prompt.
- Treating it as a separate product. A PWA should be your website with extra capability, not a parallel codebase.
For broader performance considerations, our green web design guide covers the principles that make PWAs fast and efficient.
Frequently Asked Questions
Are PWAs SEO-friendly? Yes. PWAs are websites first. Google indexes them like any other site. Done well, they often outperform traditional sites on Core Web Vitals (a Google ranking factor).
Can a PWA be in the App Store? Sort of. You can wrap a PWA with PWABuilder and submit to Microsoft Store and (with extra work) Google Play. iOS App Store remains restrictive but most users add PWAs from the browser anyway.
Will users actually install a PWA? If you prompt at the right moment (after engagement, not on first visit), install rates of 5-15% are realistic.
How long does a PWA take to build? 4-8 weeks for most UK SMEs. Faster if you're adding PWA features to an existing modern site.
Do I still need a website if I have a PWA? No. A PWA is your website with extra capability. One codebase serves both.
The Bottom Line
For most UK SMEs, a PWA delivers 80% of native app value at 20% of the cost. The technology has matured, iOS support is finally complete, and customer expectations for fast mobile experiences keep rising. If you're considering a native app, consider a PWA first.
Get in touch to discuss whether a PWA is right for your business, or explore our custom website design and web development services.
