PWAs are just push notifications, it’s an entire app system. Home Screen, offline functionality, intents to share with other apps/the web, seamless updates, etc etc etc. Not to mention that the push permission problem is easily solved, indeed is _already_ solved by Google in Chrome. A lot of it is actually an improvement on APIs like AppCache that Apple originally implemented for iOS web apps!

“a feature that is only abused for spam” is a wild misreading of PWAs. It’s true that they aren’t used too widely today but that’s _because_ Apple refuses to support it. I think it was a huge strategic misfire to create this PWA “brand” as it allows everyone to throw the baby out with the bathwater. The vast majority of the APIs involved make sense.

Above should start “PWAs aren’t”, d’oh…

Weird, I am using Chrome on Android and 99.999% of the time I don't see a popup asking me to enable push notifications.

What websites are you visiting?

Chrome is a different. Chrome shows you some notifications only after you visited it couple of times or was on site couple of minutes.

I like to think of it as bad implementations and people not considering the user experience.

Sometimes you just have project managers or clients who want it like that regardless of how awful it is. In that scenario I think it's the developer's responsibility to give push back. It's why I don't get asked about implementing pop-ups on homepages.

> I hate every time I visit a new site and there’s some dumb pop up on my browser asking me to enable push notifications.

So just don't click 'Allow'. Why should the manufacturer have to intervene here?

... because I don't want the obnoxious "let me spam you" dialog to occur at all.

A feature that's primary use case is spam, is a user hostile feature that has no business being in a browser.

That’s a UX issue with your preferred browser.