PWA vs responsive website: what should a business build?

Quick answer

Build a fast responsive website if customers mainly find you, read about you and get in touch. Consider a progressive web app if they come back often to do something, such as booking, ordering or checking an account, and would value home-screen access, offline use or notifications. Our websites start at £499; app-like builds are quoted separately.

Every few years a new term arrives that makes business owners wonder whether their website is out of date. Progressive web app is one of them. The idea is sound: a website that can be installed like an app, work without a signal and send notifications, without the cost and hassle of app stores. For some businesses it is exactly right. For most, a well-built responsive website already does everything customers need. This comparison helps you tell which you are.

What each one is

A responsive website rearranges itself to fit any screen, from a large monitor to a small phone. It is the standard for any modern business site.

A progressive web app (PWA) is a responsive website with extra technology added: a manifest file that lets people install it to their home screen, a service worker that can cache content so parts work offline, and, where supported, push notifications. The MDN guide to progressive web apps and Google’s web.dev PWA resources explain the technology in detail.

Responsive website versus PWA

When a responsive website is enough

• Customers visit to learn about you, see prices or examples, and get in touch.
• Most visits are first visits, from search, adverts or recommendations.
• There is no logged-in area, or it is used rarely.
• Your budget is better spent on content, speed and search visibility.

That describes most trades, professional services, shops with simple catalogues and local businesses. For them, a fast responsive site with clear calls to action does far more than app features. Our guide to website speed covers the part that matters most on phones.

When a PWA earns its cost

• Repeat use. Customers return weekly to book, reorder, check a timetable or view an account.
• Patchy signal. Staff or customers use it on site, outdoors or underground, where offline access helps.
• Notifications that people actually want, such as booking reminders or order updates.
• You want app-like access without an app store, and the costs, reviews and fees that come with it.

Examples include a gym’s class booking tool, a field service team’s job sheet, a café’s ordering and loyalty site, or a members’ area used every week.

The iPhone question

Android has supported PWAs well for years. Apple’s support has improved: iPhone users can add web apps to their home screen from Safari, and since iOS 16.4 installed web apps can receive push notifications if users allow them, as WebKit announced. Some features are still more limited on iOS than on Android, and the install step is less obvious for users. If many of your customers use iPhones, test the exact features you rely on before promising them, and explain to users how to install.

PWA versus native app

A PWA is often compared with a native app from the App Store or Google Play. Native apps get fuller access to device features and a store listing; they also need separate builds or a cross-platform framework, store reviews, and fees in some cases. A PWA runs from one web codebase and is found through search. Our comparison of web app development costs covers the wider decision.

Offline: useful, but design it carefully

Offline support sounds simple and is not. A PWA can cache pages and data so they appear without a signal, but someone has to decide what to cache, how long to keep it, and what happens when the cached version is out of date. A gym timetable cached last week is worse than no timetable if a class has been cancelled. A good offline design shows clearly when information was last updated, caches only what is safe to show stale, and queues actions such as form submissions to send when the signal returns. Ask any developer how they will handle stale data before agreeing to offline features.

Notifications: earn the permission

Push notifications are the feature people most often ask for and most often misuse. Browsers and phones ask the user for permission, and if they say no, you usually cannot ask again easily. The rule is to ask only when the value is obvious: after someone books a class, offer a reminder; after someone places an order, offer delivery updates. Never ask on the first page view. Send only what the customer agreed to, and make it easy to turn notifications off. A handful of useful messages builds trust; a stream of promotions gets the app removed.

What it costs

A responsive website is the base cost. Turning it into a PWA adds work: the manifest and icons, a service worker with a sensible caching strategy, offline pages, notification permission flows and the server side to send them, and testing across Android, iPhone and desktop. Simple installability is a modest addition; robust offline behaviour and notifications are a larger build. Our website cost calculator gives a starting estimate for the website itself.

Common mistakes

• Asking for notifications on the first visit, before people trust you. Most say no and many never return.
• Caching too aggressively, so customers see old prices or timetables.
• Building app features for a site people visit once.
• Forgetting the website basics: speed, clear content and search visibility still matter most.

A worked example

A climbing wall in Sheffield had a brochure website and took bookings through a separate system. Regulars booked sessions several times a week on their phones, often in the car park with weak signal. A new responsive website was built first, with the booking flow on the same domain. Once that was working, it was made installable, with the timetable cached for offline viewing and optional reminders before booked sessions. New visitors still found the wall through search; regulars got app-like convenience without an app store download. The extra build went only where repeat customers would use it.

Questions to ask before building a PWA

1. How often do customers come back, and what do they do each time?
2. Which app features would they actually use: install, offline, reminders?
3. How many customers use iPhones, and have the features been tested there?
4. Who will maintain the caching and notification logic after launch?

The verdict

Start with an excellent responsive website. Add PWA features when you have customers who return often to do something specific, and when offline access or reminders would genuinely help them. If you are unsure, you almost certainly need the website first.

Getting it built

Our custom WordPress websites are £499 one-off for up to eight pages, responsive and mobile-first. App-like tools, portals and booking systems come under our web applications service, from £1,999, quoted in writing before work starts. All our prices are on the pricing page.