Think like a user: practical UX design tips for developers
summary
Practical rules: assume users scan pages in under 3 seconds following an F-shaped reading pattern, so give a clear starting point, tight visual hierarchy, short line lengths and generous spacing. Real fixes shown: Monzo reduced payment friction by verifying sort/account numbers and adding confirmation; a delete modal becomes safer with explicit “Delete file” vs “Do not delete” and a red filled primary; Gmail’s short undo window prevents costly mistakes; what3words proves life‑saving for rural rescues. Use clear labels, feedback (loading bars, skeletons) and avoid deceptive patterns.
AI-written summary · about
chapters (30)
- 0:00Introduction to UX design
- 1:32Defining user experience
- 2:49Meeting user needs
- 4:46Beyond checklist features
- 5:56Bridging design and dev
- 7:21The Norman door concept
- 10:01UX vs UI principles
- 11:26Importance of research
- 13:21Desire paths in design
- 16:09Attention spans and time
- 17:27Scanning patterns
- 19:17Guiding user focus
- 21:57Typographic hierarchy
- 24:23The power of whitespace
- 25:46Making design obvious
- 27:28Clear language on CTAs
- 29:03Intentional friction
- 31:25Avoiding deceptive patterns
- 32:47Gestalt principles
- 35:34Navigation continuity
- 36:40Providing system feedback
- 37:57Handling error states
- 40:00Allowing user mistakes
- 41:57Guiding the user journey
- 43:07The paradox of choice
- 45:30Inclusive design
- 47:43Simple accessibility rules
- 49:25Fighting enshittification
- 51:51Making technology useful
- 53:42Case study: What3Words
related talks
46mPractical tips to elevate your UX and accessibility
52mNo Nonsense UI Design
58mDesign for Developers
38mDesign for Developers
42mDesigning for Your Users: How to Create a Better User Experience
27mWhat Makes Good UI Work: Lessons from Cognitive Psychology
01h 02mDesign for Developers
01h 01mTop 5 Things to do Today to Give Your Users a Better Experience