Push Notifications that Don’t Suck
summary
Concrete rules and examples determine whether to send a push: use silent pushes to preload content or update IP ranges, register and segment with notification channels on Oreo so users mute marketing but keep flight alerts, test deep linking and state handling so opens don’t crash, prefer short headlines (≈37 chars) and optional expanded previews, and try live/updating notifications (Guardian style) — a quick crypto-tracking prototype took about 30 minutes and proved useful.
AI-written summary · about
chapters (17)
- 0:00Start
- 5:57WTF ARE (PUSH) NOTIFICATIONS?
- 6:33NOT-PUSH EXAMPLES
- 7:19DISPLAYED VS HIDDEN PUSHES
- 9:33GCM, FCM, APNS, OH MY!
- 12:20ADDICTION
- 13:06DISTRACTIONS
- 22:48STAYING RELEVANT
- 24:35MAKING IT WORK
- 27:25STYLES
- 28:29NOTIFICATION LENGTH
- 29:25EXPAND NOTIFICATIONS
- 30:34CHANNELSE
- 32:18PRIORITY
- 32:54LOCK SCREEN
- 34:10CUSTOM LAYOUTS 4
- 35:40SUMMARY
related talks
06mPush notifications: An India perspective
46mRespecting User Attention: Notification Best Practices
28mUsing Communication APIs to enhance your UX (and reduce notifications!)
25mWhen your app is asleep
41mUniversal Pushes for Android: FCM, HMS and RuStore in One Place
19mModern Android notifications
37mEmpathetic UX with progress-centric notifications
31mThe History of Notifications Every Developer Should Know