Bringing Push Notifications to the Mobile Web
summary
Facebook implements push on the mobile web by using service workers in Chrome to receive GCM messages even when tabs are closed, with the browser or proxy browsers like UC Mini and Opera Mini registering push tokens and forwarding subscriptions to Facebook. Push increases daily use (Nokia feature phone and UC Mini launches drove significant DAU gains), Flipboard sees 75% mobile MAU growth after web launch, and service worker caching promises ~30% faster time to interact in experiments.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 0:33Agenda
- 1:18Mobile first strategy
- 2:15Mobile web is still growing
- 2:49Disadvantages of mobile web
- 4:12Why push notifications are important
- 5:25The web is an amazing platform
- 12:56Nate Schloss
- 13:20Service Worker
- 13:47Installing Service Worker
- 15:00Foreground Events
- 15:23Background Events
- 15:46Push Notifications
- 16:07Push with Service Workers
- 16:25Permission Screen
- 16:41Sending Push
- 17:20Waiting for Notification
- 17:49Waiting for Click Events
- 18:20Things to Keep in Mind
- 19:32Using Tabs
- 20:30Emerging Markets
- 21:01UC Browser
- 22:04Conclusion
related talks
23mWhen Push Comes to Web
34mThe web is getting pushy
20mEngage your Website Users with Push Notifications
38mThe web is getting pushy
55mThe Future of the Mobile Web
01h 01mAdvanced Progressive Web Apps: Push notifications under control
51mThe headless web and the future of the web on mobile.
31mThe web is getting pushy