You want an app, but you are not sure you really need the App Store and Google Play. Do you? A Progressive Web App sits right between a regular website and a native app. It runs in the browser, yet it feels and works like an installed app. In this guide you will learn what a PWA is, how the technology works, the pros and cons, and when a PWA is smarter than a native app. With a clear comparison table and real examples.
What is a Progressive Web App?
A Progressive Web App is a website built with web technology (HTML, CSS and JavaScript) that behaves like a native app. You open it in the browser, you can install it on your home screen, and from then on it works offline, loads fast and can send push notifications. One PWA runs on iPhone, Android, Windows and Mac.
The word “progressive” points to the idea that the app works everywhere, and works better as the browser can do more. A PWA is not a separate framework you pick, but a set of web standards you add to a modern website. The term comes from Google, which introduced the concept in 2015. Since then every major browser has supported the building blocks, and since 2023 Apple is fully on board too.
How does a PWA work? The three building blocks
Under the hood a PWA runs on three technical building blocks. Together they turn a regular website into something installable that keeps working offline and can send notifications. You will hear three terms: the service worker, the web app manifest and a required HTTPS connection.
- Service worker. A piece of JavaScript that sits between the browser and the network, like a smart middle layer. It stores files in a cache, which lets the app work offline and load instantly on the next visit. Push notifications and background sync also run through the service worker.
- Web app manifest. A small JSON file with the app’s name, icon, colors and start screen. This makes the “add to home screen” button possible and lets the app open full screen, without a browser bar, just like a regular app.
- HTTPS. A PWA only works over a secure connection. Service workers are powerful enough that browsers only allow them on sites with a valid certificate, for safety.
The technical details are covered in depth in Google’s PWA documentation on web.dev and on MDN by Mozilla. For most business owners the core question is not how it works, but when to choose it. The comparison below helps with that.
Progressive Web App vs native app vs website
A PWA sits between a responsive website and a native app. A responsive website adapts to the screen, but you cannot install it and it does not work offline. A native app can do everything on the device, but it needs separate builds and an app store. A PWA takes the best of both: installable and offline, yet one web app that runs everywhere.
| Feature | Responsive website | Progressive Web App | Native app |
|---|---|---|---|
| Install on home screen | No | Yes, from the browser | Yes, via app store |
| Works offline | No | Yes, via caching | Yes |
| Push notifications | No | Yes (iOS from 16.4) | Yes |
| App store required | No | No, optional | Yes |
| Discoverable in Google | Yes | Yes | Limited |
| Hardware access | Limited | Large part, browser-dependent | Full |
| One codebase for all platforms | Yes | Yes | No |
| Indicative build cost | Low | Medium | High |
| Updates | Instantly live | Instantly live | Via app store review |
The common thread: a PWA needs one codebase instead of three, and the user needs no app store. If you first want the difference between a web app, SaaS and a platform clear, read web app, SaaS or custom platform. If you are weighing a PWA against a real native app, our guide on having an app built takes it further.
The benefits of a PWA
The biggest benefit of a PWA is reach at a lower cost. You build once and run on every device, without a separate iOS and Android version. The user does not download anything from a store: a link is enough, and the app is discoverable in Google. That keeps the barrier to start low.
- One codebase, all platforms. No separate teams for iOS and Android. That saves build time and maintenance.
- Fast and offline. Thanks to caching in the service worker, the app loads almost instantly and keeps working on a poor connection. Speed matters: according to StatCounter, just over half of all global web traffic now comes from mobile devices (51.5% in June 2026), where the network often varies.
- No app store barrier and no commission. You skip the review time and the 15 to 30% commission Apple and Google charge on in-app sales.
- Instant updates. A new version is live right away. You do not wait for an app store review and users are never stuck on an old build.
- Discoverable and shareable. Every page has a URL. You share it, Google indexes it, and that is exactly what a native app lacks.
- Lighter weight. A PWA is usually a fraction of the size of a native app, so it installs faster and uses less storage.
That speed has a direct effect on your results. Deloitte’s study Milliseconds Make Millions found that improving mobile load time by just 0.1 seconds lifted retail conversion by 8.4%. A PWA is built to win exactly that. How to measure and improve load time is covered in website speed and Core Web Vitals.
The drawbacks and limitations
A PWA is not the best choice for everything. The biggest limits sit on iOS, where Safari allows less than Chrome on Android, and in hardware access. If you need deep integration with bluetooth, NFC or advanced camera features, or you are building a heavy 3D game, you will hit the edges of a PWA sooner than with native.
- iOS is more limited. Apple supports PWAs, but some APIs and background features go less far on iPhone than on Android. Always test on a real iOS device.
- No automatic app store presence. Many users still search in the store. A PWA is not there by default, though you can wrap it (for example with PWABuilder) to get it in.
- Limited hardware access. Camera and location work fine, but things like bluetooth, NFC and background tasks are browser-dependent and not available everywhere.
- Less suited to heavy apps. For graphically intensive games or apps that run constantly in the background, native offers more control and performance.
Do PWAs work on iPhone and iOS?
Yes, PWAs work on iPhone. Since iOS 16.4 (released in March 2023), Safari supports web push notifications and home-screen apps. You install a PWA on iOS through Safari’s share menu and pick “Add to Home Screen”. After that the app opens full screen, just like an app from the store.
Do watch two things. On iOS, installation only works through Safari, not through Chrome or another browser on iPhone. And a handful of advanced features stay more limited on iOS than on Android. For most content apps, portals and webshops that is no problem, but test the scenario that matters to your users on a real Apple device.
Examples of well-known PWAs
Many large brands run a PWA, often without users noticing. They choose it because one web app works on every device and is reachable without an app store. Think of Pinterest, the Spotify web player, Starbucks, Uber, Tinder and Telegram. A few numbers make clear why.
- Pinterest. When Pinterest rebuilt its mobile site as a PWA, core engagements rose 60% and user-generated ad revenue rose 44%, according to a case study by Google engineer Addy Osmani.
- Starbucks. The Starbucks PWA is roughly 99.8% smaller than the native iOS app (233 KB versus around 148 MB) and doubled the number of daily web users placing an order.
- Spotify and X. The Spotify web player and Twitter Lite (now X) are both PWAs, built to stay light and fast even on weak networks.
And Netflix? On some platforms Netflix offers an installable web app with PWA characteristics, although on TVs and phones the company leans mainly on native apps. The lesson is simple: a PWA is not a second-rate solution, but a deliberate choice by companies that put reach and speed above an app store listing.
Are PWAs still relevant in 2026?
Yes, and more than a few years ago. The biggest brake for a long time was Apple, which did not allow notifications and installation on iOS. That was solved with iOS 16.4, so a PWA now works fully on almost any device. Combined with the mobile-first reality of the web, that makes a PWA a pragmatic choice.
At the same time, a PWA is no silver bullet. For content, customer portals, webshops and dashboards it is often the smartest route. For games, or apps that reach deep into the hardware, native stays the better choice. So the question is not whether PWAs are still relevant, but whether your specific app is a good candidate for one.
When do you choose a PWA, and when native?
Choose a PWA when reach, discoverability and fast load times matter more than deep hardware access. For a webshop, a customer portal, a booking or service app, or content that also needs to rank in Google, a PWA is usually the better and cheaper choice. Choose native when you are building a game or constantly need heavy hardware features.
A handy rule of thumb:
- Choose a PWA for a broad audience, a limited budget, content that needs to be discoverable, or an app that is mostly forms, lists and transactions.
- Choose native for heavy graphics, games, intensive bluetooth or NFC use, or when a prominent app store spot is a real selling point.
- Not sure? A PWA is often the smart starting point. You reach everyone with one codebase and can add a native shell later if it turns out you really need it.
There is one more reason that often gets forgotten: ownership. A PWA runs on web standards you keep in your own hands, without depending on an app store’s rules. If you want to make that trade-off more broadly, read the complete guide to custom websites or see how a modern stack performs in Astro and Next.js vs WordPress.
What does it cost to build a PWA?
A PWA is at heart a well-built web app with an extra layer of installability and offline caching. The cost therefore tracks that of a web app, and the PWA layer itself adds relatively little: the manifest and the service worker are a matter of days, not weeks. What sets the price is the features underneath.
Put simply: the question is not “what does a PWA cost”, but “what does the app I want cost, and do we put a PWA layer on it”. Usually the answer is yes, because that layer delivers reach and speed at a low extra cost. For a realistic picture of build costs per type, our guide on having an app built helps, and for the broader approach to modern websites see our page on custom websites.
What is the first step?
- Write down what the app has to do. Not the design, but the goal and the core features. Who uses it and which action do they need to do smoothly?
- Decide your hardware needs. Do you need deep camera, bluetooth or NFC features? If not, a PWA is almost always the faster and cheaper route.
- Pick a builder who gives you the honest trade-off. A good partner also tells you when a PWA is enough and you do not need an expensive native app.
Plan a free intro call if you want to spar about the right route for your app. No sales pressure, just honest advice on PWA versus native. TopDevs is a Dutch software agency that builds custom software, AI integrations and automations, and that is exactly why we look at what you need before we build anything.
