Progressive web apps explained in plain English
What a progressive web app is, how installing and offline use work, where the limits are, and when it is a sensible middle ground for a business.
A progressive web app is a website that has been built to behave like an app. You open it in a browser like any other site, but you can also add it to your phone's home screen, launch it from an icon, and in many cases keep using it when the signal drops out.
The name is clumsy and most people shorten it to PWA. The idea is simple enough: start with a website, then add app-like abilities for the devices that support them.
What makes a website "progressive"?
Three things, roughly.
- It can be installed. The site includes a small file describing its name, icon and colours. With that in place, a phone or computer can offer to add it to the home screen or app list, where it opens in its own window without the browser's address bar.
- It can work offline. A script saves parts of the site on the device. Next time the person opens it, those saved parts load straight away, with or without a connection.
- It is secure and responsive. It runs over an encrypted connection and its layout adapts to any screen size.
"Progressive" refers to the way it adds features step by step. On an older browser it is just a website. On a newer phone it gains the extras. Nobody is locked out.
What does installing one look like?
There is no app store involved. On Android, the browser often shows a prompt offering to install the site. On an iPhone, the person usually has to open the share menu and choose to add it to the home screen, which is less obvious and worth explaining with a short instruction on the page.
Once installed, it has an icon like any other app. Tap it and it opens full screen. Updates happen quietly whenever you update the website, with no store review and no asking customers to download a new version.
How does offline use work?
The site decides what to save on the device. Usually that is the layout, the logo, the main screens and whatever data the person looked at last.
Say you run a mobile dog grooming business and your groomers use a PWA to see the day's appointments. They load it at the depot in the morning. Out on a rural property with no reception, the day's list is still there, and notes they type are held on the phone until a connection returns.
Offline does not mean everything works. Anything that needs fresh information, such as live availability or taking a card payment, still needs a connection. Good PWAs are honest about this. They show what was saved, tell you clearly that you are offline, and queue up what they can.
Where are the limits?
It would be misleading to say a PWA does everything a store app does. A few honest caveats:
- Support differs between platforms. Android has generally been more generous with PWA features than iPhone. Notifications, background activity and install prompts have all behaved differently across the two, and the details change with operating system updates. Test on both before you promise anything to customers.
- Some device features are out of reach or patchy. Deep Bluetooth work, advanced camera control and some sensors are easier in a native app.
- No store presence by default. People who search an app store for your business will not find a PWA unless you take extra steps to list it. For many small businesses that is fine, because customers arrive via the website anyway.
- Installing is unfamiliar. Plenty of people do not know they can add a site to their home screen. You have to show them.
When is a PWA the sensible middle ground?
We like PWAs for businesses whose customers or staff return often but who cannot justify the cost and upkeep of two store apps. Good fits include:
- A cafe with a regulars' ordering page that people open most mornings.
- A trades business whose crew need job sheets and checklists on site.
- A physio clinic offering patients an exercise program they follow at home.
In each case the audience is known, the task is repeated, and a browser can handle the features involved. You get the icon on the home screen and faster repeat visits, and you maintain one thing instead of three.
A PWA is a poor fit if you rely on being discovered in app stores, need heavy use of device hardware, or are building something like a game where performance is everything.
A quick test for your own idea
Before you ask for a quote on a native app, run through these:
- Would the main features work in a browser on a recent phone?
- Do your users already visit your website or receive emails from you, so you can point them to an install link?
- Is offline use limited to viewing saved information and queuing simple actions?
- Would you prefer to update one product instead of separate versions for each platform?
If you answered yes to most of them, ask your designer or developer to scope a PWA first. If it later turns out you need a store app, very little of the work is wasted. The screens, the content and the lessons from real users all carry over.