Earlier quoted context omitted.
I mean, the problem is the same one introduced since the two big mobile platforms were established: "I want to publish to IOS/Android as a native app without needing to have two separate builds to manage". PWAs make that pitch to those who already have websites to triple dip. It never has to promise to be as good as a native app, just "good enough". Does it live up to that? YMMV. It's probably fine for very simple ap…
I've built large, complex and beautiful healthcare apps as a PWA. The only two things I've ever missed from native functionality are: - background geolocation - push notifications on ios The second one was fixed recently. In contrast, from what I've seen 90+ percent of apps I see in the app stores would be better as a web page / PWA.
I’d take a decent wager that most of your users are most familiar with apps and would prefer installing full apps.
Doesn’t matter that most apps would be better suited to being a web page or PWA if that’s not where the users are. That’s kind of like saying that PCs are better at gaming than consoles. Yes, that’s true, but that’s not where the majority of users are.