Less look, more feel. Improving the user experience as a frontender
summary
Argues that front end work improves outcomes by filling gaps with concrete artifacts: a content model that maps content types to view modes so components match backend output, a prototype with vanilla HTML/CSS/JS that surfaces risky interactions and is testable, and a micro‑interaction checklist based on trigger rules feedback loops and modes. Claims prototyping prevents wasted backend work, design for the eighty percent speeds delivery, and shows a surprising demo cadence example with a 25 minute countdown to reveal complexity.
AI-written summary · about
chapters (13)
- 0:00Intro
- 8:37Customer lifecycle
- 12:10Single form elements
- 13:19Micro interactions
- 18:43What people miss
- 26:10Match the components
- 29:58Prototype
- 34:37Why
- 39:52Making the client pay for it
- 41:49Keeping things consistent
- 45:10Creating a prototype
- 46:59Interaction with developers
- 48:43Design principles
related talks
48mGet your screen together: Design skills for frontend people
29mDesigning in the Browser
01h 01mBringing Personality Back To The Web
36mUX designers /developers collaboration anti patterns
48mResponsive Design Workflow
14mDesigning UIs without a UI designer
42mBack to the Future: No More Static Mockups!
31mBridging Code and Creativity Level Up Your Game as a Frontend Engineer