The whole thing's a mis-feature. If it must exist at all, sites shouldn't be able to prompt for it, but simply advertise the functionality and let browsers add a little button or something for the user to actively engage with if they want to see a permissions prompt. Like the way browsers used to handle sites that advertised RSS feeds.
Meh, you'll just get full screen modals begging you to push the button. So long as a feature which (ostensibly) drives engagement exists, every ad based website is going to do whatever they can to get you to use it.
There are some really good use cases for it, but I think the balance is tipped by the far too many bad (for the user) use cases.
> Notification prompts are very unpopular. On Release, about 99% of notification prompts go unaccepted, with 48% being actively denied by the user.
So 99%+ are spam and the rest are probably users who accidentally hit accept.
I have to imagine many people are in the same boat.
But engagement is up 3%!
Looks like there will be some interaction required to prompt it.
That being said, hoping there's a browser-level option to just turn it off.
Is that user flow described actually a requirement somehow, or is that just an "ideal scenario"? Cause right after that it says "If you’ve already implemented Web Push for your web app or website using industry best practices, it will automatically work in Safari" and existing implementations don't require a button press that they used in their example. Facebook just pops up the browser prompts to allow or block as soon as you visit the page, as do many news sites and other stuff I don't want notifications from.
Maybe the "using industry best practices" part is key, and they somehow will block implementations like Facebook.