Push Notifications that Don’t Suck
summary
Explains why generic sale blasts fail and which APIs and UX fixes actually matter: use APNs/FCM for delivery, prefer silent push preloads to warm content, implement deep links and test state handling so a tap lands on the correct order or chat, and adopt Android notification channels so users can mute categories instead of all pushes. Notes easyJet boarding-pass and Eventbrite QR examples, cites Slack’s decision flow, and warns that fewer than ten irrelevant notifications a week from one app often triggers disables or uninstalls.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:49Problem with push notifications
- 6:05Technology behind notifications
- 9:43Human side of notifications
- 13:30Should you send a notification
- 17:11Make notifications work
- 19:20Platform guidelines
- 24:38Respect user well-being
- 27:53User control and well-being
- 29:00Summary and Q&A
related talks
41mApproaches to Improving Notification Opt-In Rates
43mAnnoying notifications don't attract crowds ...
20mNotifications: Challenges and Possible Solutions
46mRespecting User Attention: Notification Best Practices
15mNotifications: Stakes and Possible Solutions
39mOpening Keynote: Between JOMO and FOMO: You are reshaping communication.
27mDigital Well-Being: If you need to resort to alert fatigue, you’re designing it wrong.
42mDark patterns and Mobile UX Design