Get your screen together: Design skills for frontend people
summary
Argues that frontend developers need design judgment to reject unrealistic or non‑performant specs and to make small UX choices when no designer exists, showing a workflow that uses paper prototyping, low‑fidelity sketches, InVision/Figma hotspots and hallway testing to validate choices; reports delivering UX + UI for top user stories in as little as two weeks (seven‑eight days of work), producing prototypes and design‑system snippets meant to be handed off so the customer can continue — tests regularly reveal fixes before dev.
AI-written summary · about
chapters (32)
- 0:00Intro
- 0:22What is Out Systems
- 2:10Design is everyones job
- 6:15Design decisions
- 7:30Before
- 8:25User experience
- 9:38Business
- 11:20Users
- 12:30Golden Rule
- 13:45This is the moment
- 14:40Low fidelity vs high fidelity
- 15:40Fire your first shots
- 16:40Let users know
- 17:08Use examples wisely
- 17:29Give users control
- 17:55Consistency and standards
- 18:25Errors
- 19:05Recognition
- 20:03Dont be annoying
- 20:38Aesthetic minimalistic designs
- 21:10Undo button
- 21:23Help documentation
- 25:50Preparing for tests
- 27:35Timeline
- 29:26Design
- 31:10The crap rules
- 32:53Basic rules
- 34:53Brand universe
- 36:28Getting the screen together
- 37:34Making design decisions
- 40:42GUI parts
- 42:15QA
related talks
51mUX + Engineering: A Tale of Two Cities
49mCo-creating with UX and Software
32mPairing with designers to create a seamless user experience
35mA Developer's guide to the Design Process
14mDesigning UIs without a UI designer
53mLess look, more feel. Improving the user experience as a frontender
18mDesign Systems in Practice
31mThe hitchhikers guide to UXing without a UXer