In this article we see a frequent use case for notifications, where you want to send a notification only to the users in your database that match a specific condition.
I’ve seen this question several times, so I would like to give a definitive answer.
Let’s say that you have sent a notification to a recipient and then you want to remove it: how can you do that?
Subscribing users to web push notifications on your website is not enough: you also need to manage and renew their push subscriptions properly over time, otherwise you will lose subscribers.
When you hear “web push” you probably think about notifications… but that is not necessary true. In theory, the web push technology could be used for delivering messages or updates to the web app, without displaying a notification to a user.
On some browsers, the permission prompt for notifications can be displayed only after a user interaction with the website. Let’s see why some browsers enforce this rule, what happens if you don’t comply with it and how can you implement a solution that works across all major browsers.
Chrome 84 will fight abusive notifications. Let’s see what you should do to stay complaint and avoid the penalization.
Browsing the web, you may have noticed that most websites use a double opt-in process for subscribing the users to notifications. Basically these websites first show a custom prompt (designed with HTML / CSS) that asks you if you are interested in the notifications, then, when you click the subscribe button, they display another prompt (with native appearance) asking you if you really want to allow the notifications from the website. Isn’t one prompt enough?
Are you wondering what is the maximum length of text that you can include in your web notifications?
It’s easy to create segments based on the user preferred language. In this way you can send different notifications to users with different language preferences.