Many browsers can deliver push notifications even when a website is closed. Learn how to choose which websites are allowed to send you push notifications.
Pushpad offers a free tier, but it’s not a free service. So why should you prefer a paid service to a free one?
More features? Better support? I don’t know, I leave that to you. The aim of this post is to underly that free services might have an hidden cost that you must consider before making a choice.
These days we have investigated an issue related to Safari.
Sometimes it happens that you subscribe to the push notifications of a website, but after some time you don’t receive notifications anymore.
At first we thought that our system had a bug, but it’s not like that.
APNs an GCM have always provided a way to send notifications in batch.
It would be useful to see this feature for the Push API, which unfortunately doesn’t have it yet, meaning that you have to make an HTTP request for each endpoint. If you want to send a web push notification to N users at a time with a single API request you can still use a service like Pushpad which makes the hard work for you.
The working draft of the Push API currently doesn’t offer a good way to manage unsubscriptions.
The problems arise in the following scenarios:
- The user blocks the notifications from the browser preferences
- The endpoint is replaced because it has expired