Yes, You Should
summary
Argues that designers should know enough code to have meaningful handoffs and demonstrates Figma workflows that make that practical: component/variant libraries, external component files, and links to code repos and docs. Shows live demos using Google Sync (pulling images from a spreadsheet), the Figma tokens plugin for spacing/typography, and how auto layout, grids and constraints mimic—but don’t replace—CSS (no breakpoints, pixel-only units, limited wrapping). Ends with inspect/prototype tips and export/export-ready assets.
AI-written summary · about
chapters (14)
- 0:00Introduction and context
- 3:54Figma features for better collaboration
- 7:45Design systems and component alignment
- 12:00Responsive design in Figma
- 21:54Working with real data in Figma
- 27:19Common misunderstandings in design and code
- 30:00Balancing design and code alignment
- 31:09Q&A: Tables and design systems
- 33:21Q&A: Figma project setup
- 34:33Q&A: Limitations of Figma
- 36:03Q&A: Sharing designs with stakeholders
- 38:18Q&A: Bridging design and code gaps
- 40:13Q&A: Future of Figma and design tools
- 42:55Q&A: Figma's wishlist features
related talks
23mHow to create Figma design loved by developers
18mMaking the Things That Help Others Do Their Thing
14mRethinking Designer-Developer Collaboration
21mTokyo Opening Keynote
43mDesign Beyond Breakpoints
38mMastering the art of crafting code-aligned UI kits
17mThe rise of the design engineer
40mCreating illustration Systems that Work for Everyone