When Push Comes to Web
summary
Explains the exact flow: register a service worker, use PushManager to subscribe and send the subscription object to your server, then POST an encrypted payload to the vendor endpoint (Firebase for Chrome/Opera, Mozilla push for Firefox); shows that service workers live outside the page and wake to display Notification API bubbles even when the browser is closed. Notes Safari still lacks web push and claims the channel reaches about three quarters of web users. Offers concrete UX rules: delay prompts, use custom permission UI, and keep messages relevant.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:17Web Push Notifications
- 1:37History of Progressive Web Apps
- 4:27Progressive Web App
- 5:18Push Notifications
- 8:22The Service Worker and the Push Service
- 9:36Windows Notification
- 12:19Notifications Api
related talks
38mThe web is getting pushy
42mWeb Push Notification
01h 01mAdvanced Progressive Web Apps: Push notifications under control
34mThe web is getting pushy
20mEngage your Website Users with Push Notifications
24mAggressive Web Apps
23mBringing Push Notifications to the Mobile Web
58mService workers - beyond the cache
