By Alpit Patel and the aibrevo team · October 31, 2026 · 5 min read
What Is a Progressive Web App (PWA)?
Quick answer
A progressive web app is a web app that can be installed on a phone or computer and behave like a native app: its own icon, its own window, offline screens and push notifications, all from one web codebase. MDN defines it as an app built with web platform technologies that provides a user experience like a platform-specific app. Below: how a PWA works, what browsers and iPhones support in 2026, PWA vs native, and when a PWA is the right call.
Key takeaways
- MDN defines a progressive web app as 'an app that's built using web platform technologies, but that provides a user experience like that of a platform-specific app.' It runs from one codebase and can be installed, work offline and integrate with the device.
- To be installable, a PWA needs a web app manifest and must be served over HTTPS. Chromium browsers require name or short_name, 192px and 512px icons, start_url and display in the manifest. A service worker is not required to install, but most PWAs use one for offline use.
- iPhone support has grown: install from the Share menu in Safari, Chrome, Edge, Firefox and Orion since iOS 16.4, web push for Home Screen web apps since iOS 16.4, and on iOS 26 every site added to the Home Screen opens as a web app by default.
- Firefox on desktop does not install PWAs from a manifest; Chromium browsers on all desktop operating systems do, and Safari on macOS Sonoma and later offers Add to Dock.
- A PWA fits when users need an installable, offline-capable app but not deep hardware access or app store discovery. It avoids building separate iOS and Android front ends.
A progressive web app (PWA) is a web app that can be installed on a phone or computer and behave like a native app: its own icon, its own window, screens that open offline and push notifications, all from one web codebase. MDN defines it as “an app that’s built using web platform technologies, but that provides a user experience like that of a platform-specific app.”
Checked October 31, 2026. We read MDN’s PWA guides and WebKit’s release notes for iOS 16.4 and iOS 26.
How does a progressive web app work?
Three pieces turn an ordinary web app into a PWA:
| Piece | What it does | Required to install? |
|---|---|---|
| Web app manifest | A JSON file with the app’s name, icons, start page and display mode, so the device knows how to install it | Yes |
| HTTPS | The app must be served over a secure connection (or localhost while developing) | Yes |
| Service worker | A script that caches files and data so the app loads fast and can work offline, and that receives push messages | No, but most PWAs use one |
Source: MDN Web Docs, Making PWAs installable, checked Oct 31, 2026. MDN notes that Chromium-based browsers (Chrome, Edge, Samsung Internet) require the manifest to include name or short_name, icons with a 192px and a 512px icon, start_url, and display or display_override.
MDN sums up the result: “Like a website, a PWA can run on multiple platforms and devices from a single codebase. Like a platform-specific app, it can be installed on the device, can operate while offline and in the background, and can integrate with the device and with other installed apps.”
Which browsers and devices support PWAs in 2026?
| Platform | Install support |
|---|---|
| Desktop Chrome, Edge and other Chromium browsers | Install from a manifest on all supported desktop operating systems |
| Safari on macOS Sonoma (Safari 17) and later | File, Add to Dock, for any web app with or without a manifest |
| Firefox on desktop | Does not install PWAs from a manifest |
| Android | Installed as WebAPKs by Chrome on devices with Google Mobile Services and by Samsung Internet on Samsung devices |
| iPhone and iPad, iOS 16.4 and later | Install from the Share menu in Safari, Chrome, Edge, Firefox and Orion |
| iPhone and iPad, iOS 26 | Every site added to the Home Screen opens as a web app by default; users can switch off “Open as Web App” |
Sources: MDN, Making PWAs installable; WebKit, News from WWDC25. Both checked Oct 31, 2026.
Push notifications on iPhone arrived with iOS and iPadOS 16.4: “A web app that has been added to the Home Screen can request permission to receive push notifications,” and the request has to come from a user action such as tapping a subscribe button (WebKit, Feb 16, 2023). WebKit describes this feature for web apps added to the Home Screen, so plan your iPhone onboarding around that step: ask users to add the app first, then offer notifications.
PWA vs native app vs regular web app
| Regular web app | Progressive web app | Native app | |
|---|---|---|---|
| Installed icon | No | Yes | Yes |
| Works offline | Rarely | Yes, with a service worker | Yes |
| Push notifications | In supported desktop browsers | Yes, including iPhone Home Screen apps since iOS 16.4 | Yes |
| App store review | No | No | Yes |
| Codebases for iOS + Android + desktop | One | One | Usually two or more |
| Updates | On deploy | On deploy | Through the store |
| Deep hardware access | Limited | Limited | Fullest |
For the wider choice, see web app vs mobile app.
When is a PWA the right choice?
A PWA is a strong fit when:
- People return often and an icon on the home screen or desktop saves them a search, such as customer portals, booking tools and staff dashboards.
- Connectivity is unreliable, as in warehouses, event sites or field work, and screens must open and accept input offline. Our Life Line event EMS system had to run offline on site and sync when the connection returned.
- You want one codebase for desktop, Android and iPhone instead of paying for separate front ends.
- You need to ship fixes the same day without waiting for store review.
Choose native instead when the product depends on background location, Bluetooth hardware, heavy sensor use or app store search, or when users expect to find you in the App Store. Many teams start with a PWA and add native apps once usage proves the need.
What does it take to turn a web app into a PWA?
If you already have a web app, the extra work is usually modest: write the manifest and icons, add a service worker with a caching strategy that suits your data, design offline states for the screens that matter, and add push notifications if you need them. The hard part is deciding what must work offline and how to sync changes made offline without overwriting newer data. If you only have a content website, the first step is building the web app itself; see web app vs website.
Thinking about a PWA? See web app development, send us a message with who will use it and where, or book a free 30-minute call. We scope and quote in writing after the call.
Sources
All pages opened on Oct 31, 2026.
- MDN Web Docs, Progressive web apps: definition and capabilities.
- MDN Web Docs, Making PWAs installable: manifest members, HTTPS, browser support.
- WebKit, Web Push for Web Apps on iOS and iPadOS, Feb 16, 2023.
- WebKit, News from WWDC25: web technology coming this fall in Safari 26 beta: Home Screen sites open as web apps by default.