Many issues related to web push notifications can be solved by simply resetting the browser permission. That removes the old browser subscription and creates a new subscription.
In the last months we have rolled out new notification features and other performance improvements.
If you use Pushpad Pro, in order to receive the update, you should make a small change to your service worker.
This tutorial explains how to add web push notifications to a domain and to all its subdomains using Pushpad.
Some kinds of applications, such as chats, may create a lot of push notifications in a small amount of time. Sometimes you just want to notify every single message, but other times might be better to reduce the number of notifications.
A customer has recently asked if they could use SVG images as the notification icon. Unfortunately the answer is no at the moment because of browser support.
Is it possible to transfer web push subscriptions to a different domain / web push service?
We’ve all been there: you have built a great web app, optimized for mobile, but you have to build a native or hybrid web app just to send push notifications.
Fortunately, thanks to the new standards, like the Push API, Service Workers and Web Notifications, you don’t have to build an app only to have the ability to send push notifications. Now websites can send push notifications directly, even when the user is not surfing the website.
Awesome! The problem is that web push notifications work on Android, but not on iOS!
If you work with the Push API or service workers in general you know that debugging can be a pain. Fortunately Chrome has two hidden gems that can save you many headaches.