Aggressive Web Apps
summary
Shows how service worker push works, explains that almost 75% of active users can receive web push, and gives concrete wins (Arkansas Children’s Hospital cuts no‑shows 20% to 2%). Demos include the Guardian building images in the worker without canvas, and warns that current permission UIs let one bad site block all notifications. Recommends better UX and enforcement around asking for permissions; summarizes the timely, actionable, personal rule.
AI-written summary · about
chapters (24)
- 0:00Intro
- 1:04SERVICE WORKER
- 1:41APP LIKE FEATURES
- 3:26HOW TO PUSH
- 4:50HOW IS NOT THE PROBLEM
- 5:01GOOD PUSH NOTIFICATIONS
- 5:17I DON'T BELIEVE THIS
- 8:52TIME OF DAY, TIME ZONE, NUMBER OF NOTIFICATIONS
- 9:31PERSONAL
- 10:01KNOW WHEN TO BREAK THE RULES
- 11:00LET THEM OPT OUT WITHIN YOUR APPLICATION
- 12:06DEMO
- 15:26NO CONTEXT
- 16:03STOP THIS!
- 17:10DO NOT DEMAND NOTIFICATION PERMISSIONS ON PAGE LOAD
- 17:43WHEN USERS DISMISS PERMISSIONS BY DEFAULT THE WEB PLATFORM LOSES ITS POWER
- 18:09SUGGESTIONS
- 18:21FOR NOW
- 19:39FOR THE FUTURE
- 19:53SUGGESTION? BROWSERS SHOULD ENFORCE A USER INTERACTION BEFORE ASKING FOR PERMISSION
- 20:11GET INVOLVED
- 22:12PUSH NOTIFICATIONS ARE AWESOME FOR THE RIGHT THINGS
- 22:54USERS WILL BLOCK IF THEY HAVE A BAD EXPERIENCE
- 23:18BUILD PROGRESSIVE WEB APPS
