To provide some context on this, we provide clients with 4 built-in prompting options and we do our best to encourage them to use the one that is best for their user experience.
We definitely want to discourage people from asking for notification permission in an obtrusive way. It's not good for anyone when that happens. We wrote a blog post with some recommendations here: https://onesignal.com/blog/web-push-permission-prompting-cha...
I'm not sure how to put this, but your product is "abused" to such an extent that I personally took the time to pop open the Web Inspector, find the CSS selector for the notification, and use it to look up your company and mentally blacklist it and make a point of bringing it up by name when relevant: https://news.ycombinator.com/item?id=21848866. Your product is seemingly fundamentally misaligned with how users want to interact with the web, to the point where browsers are implementing behaviors that specifically target your implementation. Your blog post gives me very little confidence in your commitment to making this experience better:
> OneSignal encourages all websites to adopt a two-step prompting system if they don't already do so. This will help prevent the website from being penalized and forced to show a quieter permission prompt if too many users have denied the traditional native prompt in Chrome.
Websites are being penalized for a reason, and you know this. Simply adding another modal is just making the problem worse.
> The easiest prompt to transition to is OneSignal's Slide Prompt. Ideally, however, we encourage users to use the Custom Link prompt.
The Slide Prompt should not even be offered as a transition. It's completely at odds with the intent of this browser change, which is all about user intent. Providing facilities to present annoyances that bypass user interaction is the complete opposite of this.
> Offering a coupon in exchange for users opting-in to notifications.
…no?
Please, please, please reconsider how you are implementing these. If you are genuinely unaware of the widespread misuse of your tools, I'd be more than happy to direct you to numerous examples of zero-click, near-immediate, largely irrelevant faux notification requests coming from websites using your product.
To provide some context on this, we provide clients with 4 built-in prompting options and we do our best to encourage them to use the one that is best for their user experience.
We definitely want to discourage people from asking for notification permission in an obtrusive way. It's not good for anyone when that happens. We wrote a blog post with some recommendations here: https://onesignal.com/blog/web-push-permission-prompting-cha...