What are progressive web applications? (2026 guide)

A progressive web application, usually shortened to PWA, is a website built so that it behaves like an installed app. It runs in the browser, but it can be added to a home screen or desktop, it opens without browser controls around it, it works when the connection drops, and on most platforms it can send push notifications. One codebase, written in the same HTML, CSS and JavaScript as any web application, serves every device with a modern browser.

The interesting question is not what a PWA is, but when one is the right answer and when it quietly is not. We have built both PWAs and native apps, and the decision usually turns on three things: what the app needs to do with the device, how you expect people to find it, and whether you can justify maintaining two codebases instead of one.

What makes a web app “progressive”

Three technical pieces do most of the work, and it is worth knowing their names because your developers will use them constantly.

A service worker. A small script the browser runs in the background, separate from the page. It sits between your app and the network, so it can serve cached files instantly, queue actions taken offline and replay them when the signal returns, and receive push messages when the app is closed. Without one you do not have a PWA, you have a website.

A web app manifest. A short JSON file telling the device the app’s name, icons, colours and how it should launch. It is what allows a phone to install your app to the home screen and open it full screen rather than in a browser tab.

HTTPS. Service workers only run over a secure connection. Every site should be encrypted anyway, so this is rarely an obstacle, but it is a hard requirement rather than a recommendation.

On top of those, browsers expose a growing set of device capabilities to web code: camera and microphone, geolocation, file access, Bluetooth on some platforms, background sync. The available list differs by browser and operating system, which is the honest limitation we come back to below.

PWA versus native app

Neither is superior in the abstract. They fail in different places.

	Progressive web app	Native app
Codebase	One, all platforms	One per platform, or largely shared via a cross-platform framework
Distribution	A URL, installed from the browser	Store review
Found by Google	Yes, every screen is an indexable page	Only the store listing, not the content inside
Offline use	Yes, via service worker	Yes
Push notifications	Android and desktop; iOS once installed	Yes
Deep hardware access	Limited to browser APIs	Full
Updates	You deploy, users get it on next load	Review, then download
Platform commission	None	Fees on in-app purchases

Two rows decide most projects: discoverability and hardware access.

Discoverability works differently

A native app’s content is not crawlable the way web pages are. Its store listing can rank in Google, and individual screens can be surfaced through deep links if you set that up, but the app itself is not a set of rankable URLs. In practice people find it because they already know your brand, because you paid to advertise it, or because it ranks in the store’s own search. A PWA is a website, so it appears in Google results and opens for anyone who taps a link, without committing to a download first. Where the first interaction is a stranger arriving from a search or an email, that matters a great deal.

The reverse is also true. If people use your app daily and open it by habit, the home screen icon a native install earns is valuable, and store presence is itself a form of credibility.

Hardware and platform limits are the real constraint

Browsers have closed much of the gap, but not all of it. Background processing is more restricted on the web, and access to health data, secure biometric storage, advanced camera controls, NFC payments and some Bluetooth profiles remains patchy or unavailable. iOS is consistently the most restrictive of the major platforms.

If your product depends on any of those capabilities, a PWA is not a cheaper route to the same thing. It is a different, smaller thing, and that is the point at which we would talk to you about mobile application development instead.

What a PWA costs to build and run

The saving is real but often overstated. A PWA does not cost a third of a native app simply because it is a PWA. Most of the budget in any app goes into design, backend, integrations, testing and support, and none of that gets cheaper.

Where you genuinely save is in duplication. One codebase means one set of features to build, one set of bugs to fix and one deployment, and you avoid an app store review queue on every release. Over a few years of active development, that difference compounds.

Our published ranges apply as they would to any project: a straightforward app typically sits between £10,000 and £50,000, a mid-range product with real integrations between £50,000 and £150,000, and something complex from £150,000 upwards. UK agency rates generally run £75 to £150 an hour. Our cost estimator will give you a rough figure, and our guide to app development costs in the UK explains what moves the number.

When a PWA is the right choice

A PWA tends to be the sensible answer when:

• The app is content-led, transactional or workflow-based: bookings, dashboards, ordering, internal tools, portals.
• Search visibility matters, or people will arrive from links rather than a store listing.
• You need to reach both Android and iOS users on a single budget.
• You expect to ship changes frequently and do not want a review queue between you and your users.
• Field staff need something that keeps working in a warehouse or a rural site with no signal.

That last one is underrated. Offline capability is usually treated as a nice extra, but for anyone doing surveys, inspections or deliveries it is what makes the tool usable at all.

When it is not

A PWA is the wrong choice if you need deep or background access to the device, if you are building a game or anything graphically demanding, if your revenue depends on app store distribution and in-app purchase, or if your buyers expect to find you on the App Store and will judge you for not being there. Perception is a legitimate requirement even when it is not a technical one.

There is also a middle path. Cross-platform frameworks let you build native apps for both platforms from largely shared code, trading some of the PWA’s simplicity for full device access. Our guide to cross-platform app development covers how that compares, and native versus web goes through the basic decision directly.

Getting one built properly

The failure mode we see most often is a PWA that is really a responsive website with a manifest bolted on. It installs, then does nothing useful offline because the caching strategy was never thought through, and the first time someone loses signal the app shows an error page.

Doing it properly means deciding early which data must be available offline, how conflicts are resolved when an offline change meets a newer server version, and what the app shows when working from cache rather than live data. That is design work as much as engineering, which is why it belongs in the UI and UX stage rather than being retrofitted at the end. If you are starting from an existing site, our web application development team can assess how much of it is reusable.

Frequently asked questions

What is a progressive web application in simple terms?

A progressive web application is a website built to behave like an installed app. You visit it in a browser, but you can add it to your home screen or desktop, open it full screen without browser controls, use it when you are offline, and receive push notifications. It is written with standard web technologies, so a single codebase serves phones, tablets and computers rather than needing a separate version for each platform.

Do progressive web apps work on iPhones?

Yes, but with more limits than on Android. Safari supports the core PWA features, including installation to the home screen and offline use through service workers. Web push notifications work on iOS only after the user has installed the app to the home screen, which is an extra step you need to prompt for. Some device capabilities available to native iOS apps, such as certain background tasks and hardware APIs, remain unavailable to web code.

Are PWAs cheaper than native apps?

Usually, though not by as much as people expect. The saving comes from maintaining one codebase instead of two, and from skipping app store review on every release. Design, backend development, integrations and testing cost the same either way, and those account for most of the budget. Over several years of active development the difference is meaningful; on a single initial build it is smaller than the headline suggests.

Can a progressive web app be listed in the app stores?

Yes, with extra work. Google Play accepts PWAs packaged as Trusted Web Activities, which is a well-established route. Apple’s App Store requires the app to be wrapped in a native container and to meet its review guidelines, and submissions that are little more than a website in a shell are frequently rejected. If store presence is essential to your plan, factor that packaging and review work into the budget from the start.

Does a PWA work completely offline?

Only for the parts you deliberately make available offline. The service worker caches the files and data you tell it to cache, so anything outside that set will still fail without a connection. Deciding what must work offline, and how changes made offline are synchronised when the connection returns, is a design decision taken early in the project rather than something the technology handles automatically.

Is a PWA better for SEO than a native app?

They are not really comparable, which is the point. A PWA is a website, so its pages can be crawled, indexed and ranked in Google like any other site, and shared as ordinary links. A native app’s content is not crawlable in the same way: at best its store listing ranks, so it is mostly found through app store search, advertising or existing brand recognition. If organic search is a meaningful route to your customers, that alone often decides the question.

Talk it through with us

If you are weighing a PWA against a native or cross-platform build, we will give you a straight answer about which suits your case, including when it is not the option we would be building. Have a look at how we work, or get in touch and we will arrange a call.