Progressive web apps for small businesses: worth it?

Key takeaways

A progressive web app for a small business is a website with a few extra abilities: it can be added to the home screen, open without a browser bar, work with a poor signal and, on supported devices, send notifications. It suits repeat customers. For a brochure or lead generation site it adds little.

• A PWA is a website, not a separate product: one address, one codebase.
• Installable: customers can add it to their home screen without an app store.
• Works offline or on a weak signal by storing key pages on the device.
• Push notifications reach iPhones only once the app is added to the home screen.

What is a progressive web app?

A progressive web app (PWA) is a website built with modern browser features so that it can be installed on a device, load reliably on a poor connection and behave like an app, while still being reached through a normal web address.

The word 'progressive' matters. The site works as an ordinary website for everyone, and gains extra abilities on devices that support them. Nobody is forced to install anything. A first-time visitor from Google sees a web page. A regular customer can choose to keep it on their home screen.

• Why mobile-friendly web design is essential for UK businesses

What can a PWA do that a normal website cannot?

A PWA adds three things to a normal website: installation, offline behaviour and, where supported, notifications. They come from two technical pieces, a manifest file that describes the app and a service worker that stores pages and data on the device.

• Install: an icon on the home screen, opening full-screen without the browser bar.
• Offline: recently viewed pages, menus or order history available with no signal.
• Speed: repeat visits load from the device, so they feel instant.
• Notifications: order updates or reminders, with the customer's permission.
• Background sync: a form or order submitted offline sends when the signal returns.

Do PWAs work on iPhones?

Yes, with limits. iPhones have supported adding web apps to the home screen for years, and Apple added web push notifications for home screen web apps in iOS 16.4 in 2023. The catch is that a customer must first add the site to their home screen through the Share menu, a step many people do not know exists.

Android is more accommodating. Chrome can prompt visitors to install a PWA and supports notifications without installation. In practice, plan for a PWA to deliver its full benefit to Android users and to committed iPhone users, and make sure the plain website works well for everyone else.

• Website not working on iPhone? The usual Safari causes

What does a PWA cost?

A PWA usually costs less than a native app and more than a standard website. Basic installability and offline pages can be added to a modern site as part of an indicative £500 to £3,000 optimisation project. Ordering, accounts, notifications and background sync are application features, and take a build into the indicative £5,000 to £20,000 range or beyond.

These are market ranges, not a rate card, and the spread is wide because 'PWA' covers everything from an installable brochure site to a full ordering system. Ask for the features to be listed and priced individually so you can see what each one costs and decide which are worth having.

• how much a business website costs in the UK
• Mobile website vs app: does your business need an app?

Which small businesses benefit from a PWA?

Businesses with repeat, task-based use benefit most. A takeaway whose regulars reorder weekly, a trade supplier with account customers, a membership club, or a field team that needs job sheets on site with no signal all gain from installation and offline access.

The test is frequency. If a typical customer visits your site once or twice before buying and rarely returns, they will not install anything, and the PWA features will go unused. Spend that budget on speed, clarity and an easy enquiry route.

• Restaurant mobile websites: menu, booking and directions

When is a PWA the wrong choice?

A PWA is the wrong choice for a lead generation or brochure site, where visitors come once. It is also the wrong choice when you need deep device integration, such as Bluetooth hardware or heavy background processing, where a native app remains stronger.

There are risks to manage. A badly configured service worker can serve stale pages, so customers see old prices or menus. Notifications that are not useful get switched off and damage trust. And if being listed in the app stores matters to you, a PWA alone will not put you there without extra packaging work.

What does this look like in practice?

A pattern we see in food and trade supply: customers reorder the same things regularly, mostly from phones, and the business is considering an app to make that easier. A scoped PWA often meets the need: a saved basket, a home screen icon, order history available offline and an order-ready notification.

It reaches customers through the existing website address, so there is nothing to market separately. Global Bridge Labs (GBL) typically recommends proving demand this way first. If usage is strong after six months, the case for a native app is evidence-based. If it is not, the business has avoided a much larger spend.

• See client work
• Website Design & Development for UK businesses
• Make your website work properly on mobile

PWA checklist

• Confirm customers return often enough to install something.
• List the features you need and check each is supported on iPhone and Android.
• Make sure the ordinary website is fast and usable first.
• Decide which pages must work offline and how often they refresh.
• Plan notifications customers would thank you for, and nothing else.
• Test installation on an iPhone and an Android phone.
• Agree how stored content is updated when prices or menus change.

Next step

If customers use you repeatedly from their phones, a PWA is worth a conversation. If they do not, a faster, clearer mobile website will do more for the same money.