Progressive Web App Development in 2026: What PWAs Can Do

Updated October 2026 by the Cliffex team.

A progressive web app (PWA) is a website that users can install to their home screen or desktop, open in its own window, use offline and receive push notifications from. In 2026 PWAs work on Android, desktop and iPhone, but iOS still limits them: no install prompt, push only after the user adds the app to the Home Screen, and no access to hardware such as Bluetooth. A PWA can replace a native app when your product is mostly content, forms and dashboards; it falls short when you need deep device access or App Store discovery.

What makes a website a PWA

Three building blocks turn a responsive website into an installable app:

• HTTPS. A PWA must be served over HTTPS (or localhost during development).
• A web app manifest. A JSON file with the app’s name, icons, start URL and display mode. Chromium browsers require a name, 192px and 512px icons, a start URL and a display value before they offer installation.
• A service worker. A script that sits between the app and the network, caching files and data so the app loads fast and works offline. MDN notes that a service worker is not strictly required for installability, but almost every useful PWA has one.

What PWAs can do in 2026

Work offline with service workers

A service worker can cache the app shell (HTML, CSS, JavaScript, icons) on first visit so later launches load instantly, even without a connection. Data can be stored in IndexedDB and synced when the user is back online. The common patterns are cache-first for static files, network-first for live data, and a clear offline screen for anything that needs the network. Good offline behavior takes design work: decide which screens must work offline and what happens to actions taken without a connection.

Install on every major platform

• Android: Chrome on devices with Google Mobile Services and Samsung Internet install PWAs as WebAPKs, which behave much like store apps (MDN).
• Desktop: Chromium browsers (Chrome, Edge) install PWAs on Windows, macOS, Linux and ChromeOS. Safari 17 and later on macOS Sonoma can add any web app to the Dock. Firefox does not support installing PWAs from a manifest.
• iPhone and iPad: since iOS 16.4, PWAs can be added from the Share menu in Safari, Chrome, Edge, Firefox and Orion.

Send push notifications

The Push API is supported across major browsers and has been since March 2023. On iPhone and iPad, Apple added web push in iOS and iPadOS 16.4, for web apps added to the Home Screen, together with the Badging API for icon badge counts.

Get listed in some app stores

A PWA can be published on Google Play by wrapping it in a Trusted Web Activity, and on the Microsoft Store by packaging it with PWABuilder, with no code changes required. Apple’s App Store has no PWA route. A web app wrapped in a native shell must meet Guideline 4.2, which rejects apps that are little more than a repackaged website.

PWA support on iOS: where things stand

iOS support has improved steadily but remains the main constraint on PWAs:

• Home Screen behavior changed in iOS 26. WebKit announced that every website added to the Home Screen opens as a web app by default, with an “Open as Web App” toggle users can switch off. Previously only sites with the right manifest or meta tag opened in their own window.
• No install prompt. Chromium browsers fire a beforeinstallprompt event so a site can show its own install button. MDN marks it as non-standard with limited availability, and Safari and Firefox do not support it. On iOS, you need in-app instructions that walk users through Share, then Add to Home Screen.
• Push needs installation first. A user must add the PWA to the Home Screen before it can ask for notification permission.
• Storage. Safari can clear script-written storage for sites that go unused, but WebKit says Home Screen web apps keep their own usage counter and should not lose first-party data. From Safari 17, a browser app’s origin quota is up to 60% of total disk space. Keep the server as the source of truth anyway.

What PWAs still can’t do well

• Bluetooth and other hardware. Web Bluetooth works in Chrome but not in Safari or Firefox, so it is unavailable on iPhone.
• Reliable background work. The Background Synchronization API has limited availability and is missing from some widely used browsers. Continuous background location tracking, as a fitness or delivery app needs, belongs in a native or cross-platform app.
• App Store discovery on iOS. If users expect to search for you in the App Store, a PWA alone won’t be found there.
• Deep OS integration. Widgets, Siri and Shortcuts, HealthKit, in-app purchases through the store, and similar platform features need native code.

When a PWA can replace a native app

Your app needs…	PWA	Native or cross-platform
Content, catalogs, booking forms, dashboards, internal tools	Good fit	Possible, but more to maintain
One codebase for web, Android, desktop and iPhone	Good fit	Needs a separate web app
Instant updates without store review	Yes	No
Push notifications	Yes, on iOS only after Home Screen install	Yes
Offline use	Yes, with careful design	Yes
Bluetooth, NFC, background location, HealthKit	Limited or unavailable on iOS	Yes
App Store search and ratings on iOS	No	Yes

A common middle path is to launch a PWA first, learn what users do, then build a native or cross-platform app once you know which features justify it. If you are weighing all the options, see our native vs cross-platform vs hybrid comparison.

How we build a PWA

1. Scope the offline and install story. Decide which screens must work offline, which data is cached, and how users on iPhone will be shown how to install.
2. Build a fast, responsive front end. Usually React, with server-side rendering where search visibility matters.
3. Add the manifest and service worker. Icons, display mode, caching strategies, and an update flow so users get new versions without stale caches.
4. Add push and badging if needed, with a permission request that appears after the user sees value, never on first load.
5. Test on real devices. iOS Safari, Android Chrome and desktop browsers behave differently, especially around installation and storage.
6. Optionally package for stores via Trusted Web Activity for Google Play and PWABuilder for the Microsoft Store.

Cost and timeline

A focused PWA, such as a booking tool or customer portal, usually fits our Starter/MVP tier: $4,000–$10,000 over 4–6 weeks. A PWA with user roles, payments, offline sync and an admin panel typically falls into the Business tier at $10,000–$20,000 and 6–12 weeks. Larger platforms start at $20,000 and are scoped individually. See pricing and our cost guide. Every project includes 30 days of post-launch support, then hourly maintenance at $25–$49/hr on approved estimates.

How Cliffex can help

Our web application team builds React front ends with Node.js or Laravel back ends, and can add PWA features to an existing web app or build one from scratch. Our work on a live fantasy sports web platform shows the kind of real-time web product we build. Tell us what you need and we’ll recommend PWA, native or cross-platform with an estimate.

Frequently asked questions

Do PWAs work on iPhone in 2026?

Yes. Users can add a PWA from the Share menu in Safari and other iOS browsers, and since iOS 26 every site added to the Home Screen opens as a web app by default. There is no automatic install prompt on iOS.

Can a PWA send push notifications on iOS?

Yes, since iOS 16.4, but only after the user has added the PWA to the Home Screen.

Can I publish a PWA in the app stores?

On Google Play through a Trusted Web Activity, and on the Microsoft Store through PWABuilder. Apple’s App Store has no PWA route; a wrapped web app must offer enough native functionality to pass Guideline 4.2.

Do PWAs work offline?

Yes, when a service worker caches the app’s files and data. How much works offline depends on design choices made during development.

Is a PWA cheaper than a native app?

Usually, because one web codebase serves every platform and updates skip store review. The savings disappear if you later need features only native apps can provide, so check that list first.