The Pushpad Blog is one of the largest online resources about Web Push Notifications and related technologies.
Launched in 2015, it includes hundreds of original technical articles written by engineers with deep expertise in the field.
Google Chrome has recently released a new feature to block spam notifications and although that may seem great on paper, in reality it has the potential to destroy the Web Push technology forever.
Declarative Web Push is a new proposal to improve the Push API by removing the need of a service worker.
In this article we'll see what are the best strategies to add web push notifications to many domains or subdomains using Pushpad.
Have you ever wondered what happens to the subscribers that receive your notifications if you decide to migrate to a new domain?
Can you change the push service used by the browser? Is it possible to build and use a custom push service for delivering the web push notifications to the browser?
Sending web push notifications directly from a browser to another, using the Push API protocol, is not a secure practice. Now CORS is finally removed from all browser push services.
If you are adding web push notifications to a website, you will probably hear about VAPID. Let's see what it is and why it's useful.
When you need to send events from you application server (backend) there are various technologies that you can use.
"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?
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 is not an extensive article, but just some brief notes about PostgreSQL limitations. Finding the culprit of performance issues in not easy and these limitations were found during months of research.
Let's say that you have sent a notification to a recipient and then you want to remove it: how can you do that?
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.
There are many reasons to add a service worker to Wordpress: for example you may want to improve caching or add web push notifications. Let's see how to do that.
This tutorial explains how to add web push notifications to a domain and to all its subdomains using Pushpad.
Is it possible to transfer web push subscriptions to a different domain / web push service?
We're happy to announce that Pushpad now supports **VAPID** (Voluntary Application Server Identification for Web Push).
Today we have deployed a new version of Pushpad which improves deliverability of push notifications and make it easier to find and debug any delivery failure.
Pushpad offers a free tier, but it's not a free service. So why should you prefer a paid service to a free one?
The working draft of the Push API currently doesn't offer a good way to manage unsubscriptions.
Please select whether you consent to our use of cookies and related technologies, as described in our privacy policy. Learn more