progressive web app
/proh-GRES-iv web app/ · noun · Development · Origin: 2015
Definitions
A web application that uses modern browser features (service workers, web manifests, HTTPS) to deliver app-like experiences including offline support, push notifications, and home screen installation. PWAs bridge the gap between web and native apps without requiring app store distribution, though platform support varies (excellent on Android, limited on iOS).
In plain English: A website that can work like a phone app — it installs on your home screen, works offline, and sends notifications, all without going through an app store.
Example: We shipped a progressive web app instead of separate iOS and Android apps, cutting our development cost by 60% and reaching users without app store approval delays.
Etymology
- 2007
- Steve Jobs originally envisioned web apps as the primary development model for the iPhone before the App Store existed, foreshadowing the concept.
- 2015
- Google engineers Alex Russell and Frances Berriman coined the term 'Progressive Web App' to describe web applications that use service workers, manifests, and HTTPS to deliver app-like experiences.
- 2018
- Major browsers (Chrome, Firefox, Edge, Safari) added PWA support including install prompts and service worker APIs. Starbucks, Twitter Lite, and Pinterest launched successful PWAs.
- 2020s
- PWAs became a mainstream alternative to native apps for many use cases. Project Fugu APIs expanded capabilities to include file system access, Bluetooth, and other device features.
Origin Story
The Web App That Works Like a Native App
A Progressive Web App (PWA) is a web application that uses modern browser capabilities to deliver an app-like experience, including offline functionality, push notifications, and home screen installation. The concept was introduced in 2015 by Alex Russell and Frances Berriman, both working at Google, in a blog post that defined the characteristics of this new class of web applications: progressive (works for every user), responsive, connectivity-independent, app-like, fresh, safe (served via HTTPS), discoverable, re-engageable, installable, and linkable. The technical foundation rests on three key technologies: Service Workers (background scripts that enable offline caching and push notifications), Web App Manifests (JSON files defining icons, names, and display modes), and HTTPS. Google championed PWAs heavily, integrating support into Chrome and Android, and creating the Lighthouse auditing tool to measure PWA compliance. The appeal was clear: a single codebase that works across all platforms without the friction of app store distribution. Early success stories included Twitter Lite, which reduced data usage by 70%, and Starbucks, whose PWA achieved near-parity with their native iOS app. While Apple's slower adoption of Service Worker APIs on iOS initially limited PWA capabilities on iPhones, support has gradually improved, and PWAs are now a mainstream development approach.
Coined by: Alex Russell and Frances Berriman
Context: Defined in a 2015 blog post describing web apps that leverage Service Workers, manifests, and HTTPS for native-like experiences.
Fun fact: Twitter Lite, one of the most cited PWA success stories, was so effective that it became the default Twitter experience in several emerging markets. It loaded in under 5 seconds on 3G networks, compared to over 20 seconds for the full site, and increased tweets sent by 75%.