A progressive web app (PWA) is a website built to behave like an app: it can be added to a phone's home screen without going through an app store, it keeps working — at least partially — without an internet connection, and it can send push notifications, while still just being a website running in a browser underneath it all. Nothing about the underlying technology changes; what changes is how the browser is allowed to present it and how much of it can be saved locally.
What is a PWA, exactly?
A PWA is not a separate app built with different code — it's a regular website that meets a few extra technical requirements: it's served securely (HTTPS), it includes a small file called a web app manifest that tells the browser its name, icon and colors, and it registers a service worker, a background script that lets the browser cache pages for offline use and receive push messages. Meet those requirements and any modern browser will offer to "install" the site as an app, on Android, iOS, Windows, macOS or Chromebooks alike.
How does "add to home screen" actually work?
In plain terms, the browser lets a user save a shortcut to the website, with a proper app icon, straight onto their phone's home screen or app drawer. Tapping that icon opens the site full-screen, without the address bar or browser chrome — so it opens just like a native app would, even though it's still the same website loading in the background. There's no download, no app store review, and no separate build for each device: one website becomes the installable app for everyone.
What does offline caching mean in a PWA?
Offline caching means the service worker saves key parts of the site — the layout, the logo, recently viewed pages, sometimes a chunk of data — onto the user's device the first time they visit. So the next time they open the app with a weak signal or no connection at all, it can still load something useful instead of a blank error screen. It's rarely full offline functionality for everything; the app degrades gracefully instead of failing outright, which matters most for content people reopen repeatedly, like a booking, a menu or a dashboard.
Can a PWA send push notifications?
Yes. Once a user installs a PWA and grants permission, the same service worker that handles offline caching can also receive push notifications from a server, even when the app isn't open — a booking reminder, an order update, a new message. This is one of the main reasons PWAs get compared to native apps: notifications and a home screen icon used to be things only an app-store app could offer, and a PWA now covers both.
Why is a PWA a strong middle ground for most businesses?
For most businesses, a PWA captures most of the practical benefit of having "an app" without the cost, delay and friction of building and maintaining a separate native app.
- One codebase to build and update — the website and the app are the same project, so a fix or a new feature ships everywhere at once.
- No app-store approval or review delays — a PWA update is live the moment it is deployed, the same way a website update is.
- Lower cost to build and maintain than separate iOS and Android native apps, since there is no second (or third) codebase to keep in sync.
- Still gets the core "app-like" advantages that matter for engagement — a home screen icon, an app-style full-screen view, offline resilience and push notifications.
How is a PWA different from a native app?
A native app is written specifically for one platform (iOS or Android), distributed through the App Store or Google Play, and can access the full range of device hardware and system features. A PWA runs through the browser's engine, is limited to the capabilities web browsers expose, and cannot be listed in an app store in the traditional sense — though some platforms now allow PWAs to be packaged for store listings too. For businesses whose main need is a fast, reliable, app-like presence on a customer's phone rather than deep device integration, that trade-off is usually a good one.
Frequently asked questions
Is a PWA the same as a mobile app?
Not exactly. A PWA looks and behaves like a mobile app once installed — home screen icon, full-screen view, offline support, notifications — but it's still a website under the hood, not a program written specifically for iOS or Android.
Do I need to submit a PWA to the App Store or Google Play?
No. A PWA is installed directly from the browser, without any app store involved. Some businesses additionally package their PWA for store listings, but that step is optional, not required for it to work.
Does a PWA work without internet access?
Partially. A service worker caches key parts of the site — like the layout and recently viewed content — so the app can still open and show something useful offline, though features that need live data still require a connection.
Is building a PWA cheaper than building a native app?
Usually, yes. A PWA is one codebase that works across devices and browsers, instead of separate native codebases for iOS and Android, which reduces both the initial build cost and the ongoing cost of maintaining and updating multiple apps.