Progressive web app vs native app: which to build?
· 6 MIN READ
What a progressive web app is, real examples, PWA vs native app vs website, iOS limitations, and whether a PWA is still worth building in 2026.
A progressive web app (PWA) is a website that can be installed on a phone or computer and behave much like an app. It gets an icon on the home screen, opens full screen without browser bars, can work offline, and on most devices can send notifications. There is no app store download and only one codebase to maintain.
That sounds like the best of both worlds, and for some businesses it is. For others, a native app or a plain website is the better choice. This guide explains what a PWA is, how it compares with native apps and regular websites, where Apple's iPhone limits still bite, and how to decide.
What makes a website a progressive web app
Technically, a PWA is a website with three extra ingredients:
- HTTPS. The site must load securely. Our guide to web hosting and SSL certificates explains what that involves.
- A web app manifest. A small file that gives the app its name, icon, colours and how it should open.
- A service worker. A script that runs in the background, caching pages so the app loads fast and works offline, and handling push notifications.
With those in place, browsers will offer to install the site. On Android and desktop Chrome or Edge, users usually see an install prompt or button. On iPhone, they add it through Safari's share menu with Add to Home Screen.
Progressive web app examples
Some of the best known examples come from large companies that wanted a fast, lightweight option for customers on slow connections or low storage phones:
- Starbucks built a PWA for browsing the menu and ordering, which works on poor connections.
- Pinterest rebuilt its mobile web experience as a PWA.
- X (formerly Twitter) built a lightweight installable web version of its app.
- Uber built a lightweight web version of its booking flow for slower networks.
- Many productivity tools, from email to document editors, can be installed from the browser as PWAs.
On a smaller scale, PWAs suit things like booking tools, customer portals, field service checklists, loyalty programmes and internal business tools: anything people use repeatedly but would not necessarily download from an app store.
PWA vs native app vs website
| Website | Progressive web app | Native app | |
|---|---|---|---|
| Installed on the device | No | Optional, from the browser | Yes, from an app store |
| Works offline | Rarely | Yes, for cached content | Yes |
| Push notifications | No | Yes, with some limits on iPhone | Yes |
| Found in app stores | No | Possible on Android and Windows, difficult on Apple | Yes |
| Found in Google search | Yes | Yes | Only the store listing |
| Access to device features | Limited | Good, but less than native | Full |
| Updates | Instant | Instant | Through app store review |
| Codebases to maintain | One | One | Usually one per platform, or one cross platform |
The big trade is reach versus capability. A PWA reaches anyone with a browser and can be found on Google like any web page. A native app gets full access to the device and a place in the app stores, at the cost of a bigger build, store review and separate updates.
iOS limitations you need to know
Apple's support for PWAs has improved but still lags behind Android. Since iOS 16.4, web apps added to the iPhone home screen can send push notifications, which removed the biggest gap. Several limits remain:
- There is no automatic install prompt. Users have to know to tap Share, then Add to Home Screen, so you need to explain it.
- Notifications only work once the PWA is installed to the home screen, not in a normal Safari tab.
- Some device features, such as Bluetooth and NFC through the web, are not available in Safari.
- Safari may clear stored data for sites that have not been used in a while, so offline data should be treated as a cache, not permanent storage.
- Getting a PWA into Apple's App Store requires wrapping it as a native app, and Apple rejects apps that are little more than a website.
Is PWA still a thing?
Yes. The technology behind PWAs, service workers and installable web apps, is supported by every major browser and is used quietly by a lot of everyday software. What has faded is the hype. A few years ago PWAs were pitched as the end of native apps. That did not happen, and the term is used less in marketing, but the features are now simply part of how modern web apps are built.
Why is PWA not popular?
PWAs are more widespread than they look, because many people use them without realising. They are less visible for a few reasons:
- Most people still look for apps in app stores, not in browsers.
- The iPhone install process is hidden in the share menu, and many users never find it.
- Apple's historical limits, especially around notifications, made businesses wary.
- Large brands with big budgets often build native apps anyway, so the most visible apps are native.
Is PWA relevant in 2026?
For the right project, very much so. With push notifications on iPhone, solid offline support and installability on every major platform, a PWA covers what many businesses need from an app at a fraction of the complexity. It is especially relevant for New Zealand businesses whose audience is too small to justify separate iOS and Android builds, but who want customers to keep something on their home screen.
When a PWA is the right choice
- Customers use your tool regularly, but not necessarily daily
- You want to be found on Google as well as used like an app
- You need it to work on phones, tablets and desktops from one build
- You want instant updates without waiting for app store review
- Your budget does not stretch to separate native apps yet
When a native app is the right choice
- You need deep device access: Bluetooth, background location, advanced camera or health data
- Being in the App Store and Google Play is part of how customers will find or trust you
- You are building a game or anything that needs maximum performance
- Reliable notifications on iPhone are central to the product
- You plan to charge for the app or sell subscriptions through the stores
When a website is enough
Many businesses asking about apps actually need a good website. If customers visit occasionally to find information, book a service or get in touch, an installable app adds little. Our article on whether you need an app or a website walks through that decision, and our guide on how to make a website in NZ covers the website route from start to finish.
A simple way to decide
- Write down what customers will do with it, and how often.
- List any device features you genuinely need, not ones that would be nice.
- Check what share of your customers use iPhone versus Android.
- Decide whether app store presence matters to how customers find you.
- If nothing on the list demands native, start with a PWA. You can build native later, using what you learned.
If you are weighing a PWA against a native or cross platform app, our app development team builds both and will tell you honestly which fits. Every project gets a fixed written quote before work starts. Talk to us about your app idea and we will help you choose the right starting point.