Progressive Web Apps: Why They Never Quite Took Over
Progressive web apps promised to replace native apps for many uses. Here's why that promise only partly panned out.
Progressive web apps are websites built to behave like installed apps, capable of working offline, sending notifications, and appearing on a home screen, all without going through an app store.
What they genuinely deliver
For content-focused apps like news readers or simple tools, progressive web apps deliver a genuinely native-feeling experience while letting developers maintain a single codebase across every platform instead of separate native apps.
Why adoption stayed limited
Inconsistent support for the technology across different phone operating systems, and platform holders having limited incentive to promote an alternative to their own app stores, meant progressive web apps found a real but modest niche rather than replacing native apps broadly.
A quick way to sanity-check the decision
A short checklist tends to beat a gut feeling: what's this actually for, what happens if it doesn't work out, what's the realistic cost over a couple of years rather than just on day one, and is there a simpler option that gets 80% of the benefit for a fraction of the effort.
Running through those questions before committing tends to filter out a lot of the regret that shows up later in software & apps, where novelty and good marketing can make almost anything look essential in the moment. This ties into the broader story around third-party cookies going away.
How this plays out in practice
In day-to-day use, results tend to show up unevenly. Something can work brilliantly in one context and fall flat in another that looks superficially similar, which is part of why blanket claims about it (in either direction) tend to age badly.
The people who get the most out of this in browsers & web are usually the ones who treat it as a tool with specific strengths rather than a silver bullet. That means testing it against a real task, watching where it struggles, and adjusting expectations accordingly rather than taking either the hype or the skepticism at face value.
Where this is headed
The current state of things is very unlikely to be the final one. This is an area that's still moving quickly, and what looks like a settled best practice today can look outdated within a year or two as the underlying tools, costs, and expectations shift.
That doesn't mean it's pointless to form an opinion now, just that it's worth holding it loosely. Keeping an eye on how browsers & web evolves, rather than assuming today's snapshot is permanent, is generally the safer bet.
Where people most often get this wrong
The most common mistake isn't picking the wrong option outright; it's skipping the step of defining what “right” would even look like before comparing anything. Without that, every comparison ends up anchored to whichever feature happens to be marketed loudest. You can explore more of this under Browsers & Web.
Slowing down just enough to name the actual requirement, before getting pulled into specs and rankings, is a small habit that consistently produces better outcomes in browsers & web than jumping straight to a recommendation.
How it compares across the options on the market
Rarely is there a single dominant choice; there's usually a small cluster of options that each make different trade-offs between cost, performance, ease of use, and long-term support. The right pick depends heavily on which of those you weight most.
In software & apps especially, chasing whatever is labeled “best” in a headline is a weaker strategy than matching the options against your own actual constraints, since most “best of” rankings are written for a generic reader, not for you specifically.
The bottom line
None of this means the answer is a simple yes or no. The more useful stance is somewhere in between: understand roughly how things work, know what's good and bad about them, and make the call based on your own situation rather than someone else's summary of it.
That's a less satisfying takeaway than a clean verdict, but it's a more durable one. Browsers & Web tends to reward people who stay curious about the details a little longer than the average headline encourages, and “Progressive Web Apps” is worth revisiting once you've had a chance to see it play out in your own use. A closely related shift is happening with why websites feel slow.
How to read reviews and recommendations critically
Any single review, including this one, reflects one set of priorities and one use case. A glowing recommendation from someone with different needs, budget, or tolerance for friction may simply not transfer to your situation, even if the underlying facts are accurate.
The more useful approach in browsers & web is to look for the specific reasoning behind a recommendation, not just the verdict, and check whether that reasoning actually applies to your own circumstances before treating it as an instruction.
What to look for if you're evaluating this yourself
If you're trying to decide how much weight to put on any of this, it helps to look past the top-line claim and ask a few concrete questions: what does it actually cost, who benefits most from it, and what happens in the cases where it doesn't work as advertised.
It's also worth checking whether the claims being made are specific and testable, or vague and aspirational. Specific, falsifiable claims are usually a better sign than confident-sounding generalities, regardless of how polished the presentation is or how it's framed within browsers & web.