Glossary · Web Development

Progressive Web App

pruh-GRESS-iv web apnoun

A progressive web app is a website that can be installed and behaves like a native mobile app, including offline use.

Part of speech
noun
Pronunciation
pruh-GRESS-iv web ap
Origin
The term was coined by designer Frances Berriman and Google engineer Alex Russell in 2015 to describe web apps that behave like installed native apps.

What is Progressive Web App?

A progressive web app, commonly called a PWA, is a website built with standard web technologies that can be installed on a device and behaves much like a native mobile or desktop application. Once installed, it can appear as an icon on the home screen, launch in its own window without the usual browser interface, send push notifications, and continue to work even when the device has a poor connection or no connection at all. The goal is to give users the convenience and reliability of an app without requiring them to visit an app store or download a large package.

The technology that makes this possible centers on a few components. A service worker is a small script the browser runs in the background, separate from the web page, that can intercept network requests and serve cached files. This is what allows a progressive web app to load instantly and function offline, because the service worker can respond with stored content when the network is unavailable. A web app manifest, a simple file describing the app's name, icons, colors, and display preferences, tells the device how to present the installed app. Together these pieces let an ordinary website graduate into something that feels installed and dependable.

The term was coined in 2015 by designer Frances Berriman and Google engineer Alex Russell to describe web apps that progressively gain app-like capabilities as the browser and device support them. The word "progressive" is meaningful: the same site works as a normal web page for everyone, and layers on enhanced features such as installation and offline mode only where they are available. This graceful approach means a business does not have to choose between reaching every visitor and offering a premium experience, because both audiences are served by the same codebase.

For a business, the practical stakes are reach, cost, and engagement. Building and maintaining separate native apps for different platforms is expensive, and app store friction means many users never install them. A progressive web app is discoverable through search like any website, shareable with a simple link, and installable in a couple of taps, which lowers the barrier to becoming a repeat visitor. Faster loads and offline resilience tend to improve retention and conversion, particularly on mobile connections that are slow or intermittent. Push notifications, where supported, give a channel to re-engage users that previously belonged only to native apps.

The nuances are worth understanding before committing. Support for advanced PWA features has historically varied across browsers and operating systems, so a business should verify that the capabilities it depends on are available to its actual audience. A progressive web app is not a substitute for good fundamentals: it still needs responsive design so it adapts to every screen, and it still must meet performance benchmarks such as Core Web Vitals to feel fast. A common mistake is bolting a service worker onto a slow, bloated site and expecting it to feel like an app; the offline layer amplifies whatever quality is already there. Done well, a PWA blends the openness of the web with the polish of installed software, a compelling combination for many businesses.

Why it matters

A PWA can deliver an app-like experience without app store costs, improving engagement and reach, especially on mobile and in low-connectivity markets.