Blog / How the internet works /
Progressive web apps vs native apps
Short answer: if your product is mostly content, forms or simple tools, a progressive web app (PWA) is usually the cheaper, faster route and gets you very far. If it relies on deep phone features, heavy graphics or the app-store audience, build native. Plenty of businesses should start with the PWA and see if they ever need more.
What each one is
A native app is built for one platform, typically Swift for iPhone or Kotlin for Android, and distributed through the App Store or Google Play. It installs on the device and can use almost everything the phone offers.
A progressive web app is a website with extra abilities. It runs in the browser, but can be added to the home screen, open in its own window, work offline and, on supported platforms, send push notifications. There’s nothing to download from a store: you visit the site and install it from the browser. I explained the basics in progressive web apps explained.
A third option, cross-platform frameworks like React Native or Flutter, write one codebase that becomes real native apps. It sits between the two.
At a glance
| PWA | Native app | |
|---|---|---|
| Built with | Web tech (HTML, CSS, JavaScript) | Platform languages or a cross-platform framework |
| Distribution | A web address; installable from the browser | App Store, Google Play |
| Development cost | Lower, one codebase | Higher, often two versions |
| Updates | Instant, like a website | Through store review and user updates |
| Offline | Yes, if you build it | Yes |
| Device features | Growing but limited | Full access |
| Discoverability | Search engines and links | Store search, plus store promotion |
| Install friction | Very low | Higher; people hesitate to download |
| Performance | Good for most apps | Best, especially for graphics |
What matters day to day
1. Who are your users and what do they use?
On Android, PWAs are well supported. Chrome can offer an install prompt, and the result behaves much like an app. On iPhone, PWAs are supported but with more limits. Apple allows adding to the home screen, and added web apps have been able to receive push notifications since iOS 16.4, but installation isn’t prompted as smoothly, and some features lag behind Android. In early 2024 Apple briefly planned to drop home-screen web apps for EU users, then reversed it after pushback. It showed that PWA support on iPhone depends on Apple’s choices.
If most of your users are on iPhone, test carefully before betting on a PWA.
2. What does the app need to do?
Ask about the features, not the label.
- Content, bookings, catalogues, dashboards, forms: PWA is fine.
- Notifications: possible with PWAs, with platform caveats.
- Camera, location, files: available through browser features, with permission.
- Bluetooth, background tasks, deep system integration, widgets, advanced sensors: native territory.
- 3D games or heavy real-time graphics: native.
- Payments with Apple Pay or Google Pay: both can work on the web, but check your payment provider.
3. Do you need the app stores?
Stores bring discovery, trust and a payment system, and also rules, review times and fees. Some audiences simply expect to find you there. Others never visit the store at all and just follow a link. On Android, a PWA can be packaged and listed in the Play Store; on Apple’s store, the rules are stricter about simple website wrappers.
If your customers arrive from search, social media or a message link, a PWA fits naturally. You can send a link and they’re in. No download, no waiting, no storage cost on their phone, which matters when people have limited data or space. In Nigeria and many other markets, where data is expensive and phones often have limited storage, a light web app can be kinder than a 100MB download. See mobile data prices in Nigeria over the years for context, and phone storage: why 128GB disappears so fast.
4. Cost and speed
One codebase, one deployment, updates the moment you publish. A small team can maintain it. Native work often means two platforms, store accounts, review cycles and more specialist skill. For a small business, that difference decides things.
5. SEO and sharing
A PWA is a website, so search engines can index it, and people can share links to it. A native app’s content is mostly invisible to search, unless you link app content to web pages. If discovery through Google matters to you, that’s a real advantage. For a site owner this is the strongest argument, since you already know how to optimise pages. Do check server-side vs client-side rendering for SEO if your app is heavy on JavaScript.
What a PWA needs to qualify
- HTTPS. Required. See how HTTPS works, simply.
- A web app manifest, a small JSON file with the name, icons and colours. See JSON explained for non-developers if the format is new.
- A service worker, a script that handles caching and offline behaviour.
- A responsive design that works on phones.
These are the mechanics behind “Add to Home Screen”. Be wary of caching mistakes: a badly written service worker can leave users stuck on an old version.
Common mistakes
- Building native because “everyone has an app”. Many don’t need one.
- Expecting a PWA to do everything a native app does. Know the feature limits first.
- Ignoring iPhone testing.
- Forgetting the web basics: speed, accessibility, clear navigation.
- Wrapping a poor website in an app and calling it a product.
Pick a PWA if…
- Your product is content, commerce, booking, productivity or a tool.
- You want one codebase and fast updates.
- Search discovery and shareable links matter.
- Budget and time are tight.
- Your users have limited storage or data.
Pick native if…
- You need deep device features or top performance.
- Your audience expects you in the app store.
- Your business model relies on in-app purchases or store promotion.
- You have the budget to build and maintain separate versions.
Key takeaways
- A PWA is a website that can be installed, work offline and run in its own window.
- It’s cheaper, faster to update and searchable; native has more power and store reach.
- iPhone support is the main constraint; test there first.
- Start with the PWA for most content and tool projects, and move native only when a real need appears.
Related reading
What would your app need to do that a website can’t?