“Web Push Notifications” is a general term to refer to the push notifications sent by websites and web apps. However, if you are looking for an official document that defines the “Web Push Notifications” standard, you won’t find it. This is because this technology is made up of different technologies, each one serving to a specific purpose. Let’s find out what these technologies are and where the official standards are located (documentation).
Are web push notifications a good technology for privacy?
If you are a beginner with web push notifications, you may wonder what happens to the notifications sent when the client is offline or the device is turned off. What is the behavior of the notifications in this case? Do they get delivered or are they lost?
When you send a web push notification, you need to set the TTL: what is it? What value should you use? This article describes the TTL and the best practices for setting its value.
In order to send push notifications from a website to a browser, you need to use a push service, as defined by the W3C Push API: let’s see a list of push services for the major browsers and how they work.
This article describes a simple and effective method for debugging web push notifications on a specific browser using Pushpad.
Breaking news: the standard for web push notifications (Push API) will be available soon on iOS and Safari.
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.
Are you wondering what is the maximum length of text that you can include in your web notifications?
Why some web push notifications are not delivered to the browser? Why some notifications are not displayed to the user?
A notification that is successfully delivered to the browser push service, may not reach the end user for various reasons:
Now you can use Pushpad for delivering time-sensitive messages. For example you can notify urgent alerts or incoming phone calls.
This article investigates one of the reasons that negatively impact delivery rates for web push. First it shows that web push subscriptions can last many years without expiring, then it proves a negative correlation between the age of a web push subscription and its expected delivery rate.
You can change your notification preferences for a website at any time. You can allow or block the notifications using the browser preferences:
Many developers have asked if they can use Pushpad for sending push notifications to their hybrid mobile apps. Basically they want to use the W3C Push API inside a WebView. That would make sense, because a WebView is a sort of browser embedded inside an application.
You can use the Push API to send timely notifications from your website (the notifications are delivered even when the user is not on your website). If you use Pushpad, a service for web push notifications, it is very simple to set the time when the notification must be delivered.
This tutorial explains how to add web push notifications to a domain and to all its subdomains using Pushpad.