I'd say there's a difference between a 'web site' and a 'web app'. If there's a web app for which you'd allow notifications if it was a native app, why wouldn't you do so for the web app?
Because every single website I visit today on my desktop shows me a popup asking me to enable their desktop notifications.
Nah, useless functionality. I've got feedly if I'd like to keep track of their news.
That being said I work in ad arbitrage, so I understand the presumed efficiency of these notifications. As they say our business is middle-aged Americans who can't use the Internet.
> Because every single website I visit today on my desktop shows me a popup asking me to enable their desktop notifications.
I know what you mean, but that's usually traditional news sites and the like. Having the Spotify web app notify you of the currently playing song or a remainder app reminding you of an appointment is of course a different case, Hence the "web site" vs "web app" distinction I made.
I don’t know: frankly I find them incredibly annoying (that includes Spotify, email and the likes).
But besides the point: imo the semantics of these notifications severely differ between applications. Moreover, the usefullness of them heavily depends on the ability for someone to integrate them in the whole ecosystem.
Thus notifications from news websites fit right in: they don’t need a snooze button as it in for OS X Calendar app. But they are the least useful.
So we are back to square one: if you allow notifications, then what kind of? Do you allow any HTML payloads or only some?
That being said my reply is re. subj.: I understand why Apple doesn’t like them. Because they are generally useful only for a small amount of use-cases, 99% of which is spam. And an average user is going to blame Apple for allowing him to accept them in the first place.
But all that is very much true for native app notifications as well. So it may be that you don't like notifications in general, not PWA notifications specifically?
