Design handover - tips & tricks
summary
Design handover is a process, not a moment: involve developers early, give complete specs (fonts, colors, components, animations) and ship style guide and user flows so developers stop guessing. Uses Sketch/Figma, Avocode/Zeplin for asset export and inspection, Principle for animations but Principle exports visuals only so annotate timings. Common failures: missing loading/error/edge-state designs (e.g. "two million results"), scattered component iterations, overflowing Slack from questions.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:58Matea introduction
- 2:26What is design handover
- 3:37Mistakes
- 5:29Accountability
- 6:24Developer involvement
- 8:58Tools
- 9:42Design handover tools
- 16:20Questions
related talks
45mDesign Tools and Handoffs*
48mDesign Tools and Design Handoffs — Closing the Gap Between Design and Development
20mDeath to Handovers!
49mDesign Tools - Closing the Gap Between Design and Development
45mHow to train your designer?
21mFrom handoffs to upstream
14mRethinking Designer-Developer Collaboration
35mA Developer's guide to the Design Process