Coding Outside the Box: The Developer's Role in User Experience and Design Systems
summary
Argues that developers must measure and shape UX using concrete signals: heat maps, analytics and quick experiments rather than vague best practices; lists collaboration tools — Figma file, Red Pen, Mural, Zeplin, Bitrise and Widgetbook — for raising inconsistencies and iterating. Gives concrete UI critique: YouTube Music search duplicates the magnifier action, uses a confusing trailing arrow autocomplete, and forces dictation focus differently than Spotify, causing accessibility and loading tradeoffs. Recommends judgment, rapid MVPs and feedback loops to prove changes with numbers.
AI-written summary · about
chapters (8)
- 0:00Introduction and agenda
- 1:07Psychology in UX design
- 3:14Measuring user behavior
- 8:53Developer role in UX
- 11:44Design systems and collaboration
- 14:11Judging UX in market leaders
- 18:21Adding value as a developer
- 19:46Resources and closing
related talks
37mCoder Meets Designer: Reconciling Design (...)
29mDesigning with Code in Mind
31mDesign Through a Developer's Eyes
54mDesigners vs Developers: Who is in control here?
39mDesigners x Developers: Is It a Match 💙 or a Fight 🥊?
20mInvisible Design Systems
23mDevelopers, start designing!
15mDesign + Code = Love