Behind The Screen: The Humans Who Use Our Code
summary
Android runs on cars, gym equipment, kiosks and phones and categorizes into consumer apps, commercial tools, internal solutions and hidden Android that users don’t notice; accessibility needs are permanent, temporary or situational and app updates can break muscle memory and manuals. Small UX choices matter: Twitter-esque inline hints (double‑tap DMs) work better than full product tours, ads and non-dismissible dialogs interrupt flow, forcing portrait or changing system back behavior harms users, and Android 13’s themed icons show when opt‑in defaults help. Ask why before shipping.
AI-written summary · about
chapters (12)
- 0:00Introduction and setup
- 0:52Types of Android users
- 3:42User interaction differences
- 5:24Caring for your users
- 7:52App updates and user impact
- 9:57Teaching users effectively
- 12:45Educating users without disruption
- 15:30Balancing monetization and usability
- 16:53Dark patterns to avoid
- 19:22Customization and settings
- 21:47Key takeaways and advice
- 23:11Q&A and closing
related talks
23mBeyond the Smartphone: Android’s Identity Crisis in 2026
22mApp forHumans, not machine
17mAndroid: those little details that make the difference
23mAndroid Complexity
46mOpening Keynote: Android Then & Now
29mHow Android Automotive Helps Us to Design and Build In-Car User Experiences
44mKeynote - The Future of Android...And How to Prepare For It
34mIs your app for everyone? A primer on accessibility for Android