Web Push
Setting up Web Push
The VAPID keys, the service worker and subscription storage for browser notices.
Before you start
Generate the VAPID key pair once and treat it as long-lived. Decide which page of your portal asks for notification permission, ideally after a client has done something that makes notices useful.
Steps
Each channel installs disabled, so nothing is sent before these steps are done.
Generate the keys
Create a VAPID key pair and store it in the Reach Web Push credential.
Add the service worker
Add a service worker to your portal that displays the notification payload.
Store subscriptions
Deploy the subscribe workflow and post each browser subscription to it from your server.
Set the defaults
Choose the default title and the page a click opens.
Go live
Deploy the dispatcher, enable the channel and send a notice to a staff browser.
Chrome, Edge, Firefox and Safari are trademarks of their owners, named here only to identify the service this package connects to.
See it on your own systems.
A demo takes an hour, on your data landscape rather than ours.