It’s easy to create good looking products, but what about useful ones
summary
Argues that developers must prioritize UX before UI and code, using concrete methods: heuristic evaluation with steps (define scope, know end user, choose heuristics, set up reporting, analyze findings), plus user interviews, card sorting, wireframes, component libraries and design systems, and mining support logs. Names the canonical 10 usability heuristics (Nielsen/Norman, 1995) as the checklist to find concrete failures like missing undo, poor status visibility, inconsistent icons, or tiny fonts. Promises practical examples and simple fixes developers can apply immediately.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 6:03Bad example
- 10:58What is UI
- 14:15Heuristics
- 17:25Usability heuristics
- 21:14Consistency and standards
- 23:12Arrow prevention
- 24:24Recognition vs Recall
- 25:30Flexibility and Efficiency
- 27:03Minimal Design
- 29:55Help Users
- 31:08Help Documentation
- 32:05Testing Users
- 33:40Dont follow the Hippo
- 34:43Conduct user testing
- 35:54Collaborate
- 36:07Lunch break
- 36:27Designers mindset
related talks
25mIt's easy to create good looking products, but how about useful ones?
28mIt’s Easy to Create a Good looking Product, but What About a Useful One?
28mIt’s easy to create a good looking product, but what about a useful one?
44mIt’s Easy To Create A Good-Looking Product, But How About A Useful One?
28mEleftheria Batsou-UX vs UI: It’s easy to create a good looking product, but what about a useful one?
20mThe Power of UX Heuristics in Open Source Projects
46mFundamentals of UX Design and Usability
33mBeyond Buttons: Crafting Satisfying & Easily Marketable Products