Using Communication APIs to enhance your UX (and reduce notifications!)
summary
Apps send too many alerts so users ignore them: users get 46 notifications a day and only 4.6% are actioned, so push can’t start reliable flows. Communication APIs (Vonage-style REST and SDKs for Android/iOS/back end) let apps use SMS (a claimed 99% SMS read), app-to-phone voice, and in-app video with session/publisher/subscriber models. Examples: SMS stock alerts that work without the app, in-app voice to a museum help desk, and one-to-one video GP calls.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker intro
- 6:47The notification problem
- 13:06What are communication APIs
- 18:02SMS alerts use case
- 20:54Help desk voice calls
- 23:24Video chat for healthcare
- 26:16Reducing notifications with APIs
- 27:22Closing and Q&A
related talks
38mPush Notifications that Don’t Suck
30mMarketing Automation Tools and App Engineers — Automating Pushes and Notification Dialog Operations
25mWhen your app is asleep
01h 12mThe Entertaining Life in the Notification Panel
06mPush notifications: An India perspective
46mRespecting User Attention: Notification Best Practices
19mModern Android notifications
25mWhat's new in the Android OS User Interface
