Depends on your priorities. For people into standards and commoditization, PWAs are awesome because they reduce the ability of HW makers to differentiate.

For people who just want the best possible app/phone experiences, PWAs are awful.

For lots of use cases, you'd be unlikely to notice a difference in quality. For example, I tune my guitar using a PWA, and I doubt anybody would notice the difference.

The real differentiator with native vs pwa is their ability to track the user.

PWAS are pretty good for high frame rate games, then?

I didn't say they were perfect for every use case. I'm not a gamer, so I'll have to take your word for it. But look at your own phone. You really telling me most of your apps couldn't just be PWA?

> Give me native apps any day.

Heavens no. I do not want to be forced to install an app for every single little thing - it's wasteful, detrimental to my security and privacy. Small examples from a recent trip: in Andalusia, there's a bunch of cities with very interesting old buildings (cathedrals, castles remaining from the Muslim era converted by the Spanish monarchs later on, etc.). Each and every one has a different app for their audio guide, map, etc. to help you navigate and understand them. It's just stupid, it's a one time thing and it could easily be served by a website; instead you have to download a 30-40 MB app for each one, and then remember to delete it afterwards.

They don't need apps - they just need websites. I didn't say get rid of websites. Hope you enjoyed your trip!