CommunicationLive

Notifications API

A demo of the full Web Push flow: the browser generates a subscription signed with the VAPID public key, the backend signs every send with the private key through web-push, and delivery happens via the Service Worker's push event — which is why the notification arrives even with the tab or the browser closed. The demo walks through the three real steps of the flow (permission → device registration → test send) and, being a demo, keeps subscriptions in server memory instead of a database.

Push API Notifications API Service Worker VAPID Web Push Protocol

Technologies

  • Push API
  • Notifications API
  • Service Worker
  • VAPID Signing

Architecture

  • Push API + Notifications API
  • Service Worker
  • VAPID Signing

Concepts

  • Push subscription
  • Background delivery via Service Worker
  • Browser permission lifecycle
  • VAPID signing
  • Web Push Protocol

Demo area

The demo is 100% functional — try it now.