The short answer
- A progressive web app is a website that can be installed to the home screen, work offline through a service worker and send push notifications.
- On iPhone, a PWA is installed through the browser’s Add to Home Screen option, and it can send push notifications only after it has been installed.
- Choose native when you need Bluetooth, background location or background tasks, dependable offline storage for large amounts of data, or a listing in both app stores.
A progressive web app (PWA) is a website built so it can be installed to a phone’s home screen, open in its own window, work offline and send push notifications, all from a single web codebase. On Android, a PWA comes close to a native app for most business uses. On iPhone it can install, work offline and receive push notifications, but it has less access to the device and almost no ability to run in the background, so native apps remain the better choice for anything that depends on hardware, background work or store presence.
What makes a website a progressive web app
Three pieces turn a website into a PWA. A web app manifest is a small file that gives the app its name, icon, colours and how it should open. A service worker is a script the browser runs separately from the page, which can serve pages and data from a cache when there is no connection and receive push messages. HTTPS is required for both. Everything else is ordinary web development, which is why one team can build a PWA for every platform at once.
A PWA is still a website. People can use it in a browser tab without installing anything, share a link to any screen and get every update the next time they open it. On a desktop computer, Chrome and Edge can install it too, and Safari on a Mac can add it to the Dock.
What a PWA can do on Android and iPhone
The gap between the two platforms is wider than the gap between a PWA and a native app on Android. This table reflects current versions of Chrome on Android and Safari on iOS. Browser support changes with each release, so check the specific features you need before you commit.
| Capability | PWA on Android | PWA on iPhone | Native app |
|---|---|---|---|
| Install to home screen | Yes, and the browser can prompt | Yes, manually through the browser’s Add to Home Screen option | Yes, from the App Store or Google Play |
| Push notifications | Yes | Yes, once added to the home screen and permission is granted | Yes |
| Works offline | Yes, through a service worker | Yes, through a service worker, though stored data can be cleared | Yes, with full control of local storage |
| Background sync | Partly, in Chrome | No | Yes, within the operating system’s limits |
| Location while closed | No | No | Yes, with permission |
| Bluetooth and NFC | Yes, through Web Bluetooth and Web NFC in Chrome | No | Yes |
| Camera and photos | Yes | Yes | Yes |
| Passkeys with Face ID or fingerprint | Yes, through WebAuthn | Yes, through WebAuthn | Yes, plus wider use of biometrics |
| Home screen widgets | No | No | Yes |
| Store listing | Google Play, packaged as a Trusted Web Activity | Only inside a native wrapper | Yes |
| Updates | Instant, on the next visit | Instant, on the next visit | Through store review, then installed by the user |
The iPhone limits in detail
Apple has added many PWA features to Safari in recent years, and web push, which arrived in iOS 16.4, closed the largest gap. Several limits remain that matter in practice.
- No install prompt. People have to find the Add to Home Screen option themselves. Many need to be shown how, so your site has to explain it.
- Push only after install. A PWA cannot ask for notification permission until it has been added to the home screen, and the request has to follow a tap or similar action from the person.
- Storage can be cleared. Safari may delete data stored by websites that have not been used for a while. Web apps added to the home screen are treated more generously, but storage on iPhone is still less dependable than in a native app, which matters for anything offline-first.
- Little background work. A PWA on iPhone cannot sync in the background or follow the person’s location while it is closed.
What a PWA can do on iPhone depends on what Apple supports in WebKit, the engine behind Safari, so the list can grow with each iOS release. Plan around what works today.
Store presence and discovery
Being in the App Store and Google Play matters for some products and not at all for others. A consumer app that people search for by name benefits from a store listing, ratings and the trust that comes with them. Internal tools, customer portals and booking systems are usually reached through a link in an email or on a website, so a store listing adds little.
On Android, a PWA can be published to Google Play by packaging it as a Trusted Web Activity, which shows the web app full screen inside a thin native shell. On iPhone there is no equivalent. Wrapping a website in a web view and submitting it risks rejection under Apple’s minimum functionality guideline, as covered in our guide to passing app review first time.
Cost and maintenance
A PWA is usually the cheaper option to build and to run. There is one codebase, built with web skills, and every user gets an update the next time they open it, with no store review and no old versions left in use. Payments taken on the web follow your payment provider’s terms instead of the stores’ in-app purchase rules.
Native apps cost more because there are two platforms to build for, or one cross-platform codebase with platform-specific work, plus store accounts, review and a yearly cycle of operating system changes. The trade-offs between separate native apps and a shared codebase are covered in native or cross-platform.
When each one fits
Choose a PWA when
- People reach the product through links, email or a website, rather than by searching a store.
- The main tasks are forms, lists, bookings, dashboards and messages.
- You want to test demand before paying for native apps.
- Offline use is occasional and the data involved is small.
Choose native when
- The app depends on Bluetooth, NFC, background location or other device features, especially on iPhone.
- People must work offline for long periods with a lot of data, such as records and photos on a building site.
- Notifications and background updates are central to the product on iPhone.
- Your customers expect to find you in the app stores.
Estimark sits in the second group. It has web, iPhone and Android apps, and it works offline on site by saving to the phone first and syncing later, the pattern described in offline first. On iPhone, a PWA could not make the same promise about work stored on the device.
The choice is also reversible. A product can start as a PWA and add native apps later, reusing the same API, data and design, and the web version can stay for people who work at a desk. Building the API first, with the web and mobile apps as clients of it, makes that later step much cheaper.
Questions people ask
Can a PWA be listed in the App Store?
Not directly. To appear in the App Store, a PWA has to be wrapped in a native app, and Apple may reject a wrapper that adds nothing beyond the website. Google Play does accept PWAs packaged as a Trusted Web Activity.
Do PWAs work offline on iPhone?
Yes. A service worker can cache pages and data so the app opens and works without a connection. Safari may clear stored data from sites that have not been used for some time, so a PWA on iPhone should not hold unsynced work for long periods.
Is a PWA cheaper than a native app?
Usually, because one web codebase serves every platform and updates need no store review. The saving shrinks if you later need native apps anyway, so decide based on what the product must do in its first year.
Can a PWA use Face ID?
Indirectly. A PWA can use passkeys through the WebAuthn standard, and the phone may confirm the passkey with Face ID or a fingerprint. It cannot use biometrics for other purposes, such as protecting data stored on the device, in the way a native app can.