UI Design · Lesson 12 / 12
Design handoff
How to prepare design files so developers can build them accurately: file organisation, components and variables, specs, all the states and edge cases, responsive behaviour, annotations, assets and design QA.
5 min read · 5 quiz questions
What is handoff?
Design handoff is the process of giving developers everything they need to build a design as intended. Done badly, it leads to guesswork, endless questions, and a product that looks "almost right". Done well, it's fast and the built product matches the design.
Despite the name, handoff should not be a single moment where designers throw files over a wall. The best teams collaborate continuously: developers join design reviews early, and designers stay involved during the build.
Organise the file
- Use a clear page structure: Cover, Ready for dev, In progress, Archive/Explorations.
- In Figma, mark frames or sections as Ready for development so they appear in Dev Mode.
- Name frames by screen and state:
Checkout / Payment / Error – card declined. - Name layers meaningfully — developers will see them in inspect panels.
- Remove or archive old explorations so there's only one source of truth.
- Add a changelog or version notes when you update a screen after handoff.
Use the system, not one-offs
Developers implement components and tokens, not pictures. The more a design uses the design system, the faster and more accurate the build.
- Use components and instances from the library — avoid detached copies.
- Apply variables/styles for colour, typography, spacing and radius instead of raw values.
- Use auto layout so padding, gaps and resizing behaviour are explicit (it maps closely to CSS flexbox).
- If you need something new, flag it clearly as a new component or variant to be added to the system.
Common mistake: Values that are almost the same as tokens — 15px instead of 16px, #1570F4 instead of #146EF5. Developers either copy the wrong value or have to ask. Use the tokens.
Design every state and edge case
Most handoff problems come from things that weren't designed. Before handing off, check:
| Category | Include |
|---|---|
| Component states | Hover, focus, active, disabled, selected, loading, error |
| Screen states | Empty (first use, no results), loading (skeletons), error (offline, server error), success |
| Content extremes | Very long names, very short content, missing images, large numbers, many items |
| Permissions | What different user roles see; locked or upgrade states |
| Localisation | Longer translations, right-to-left (Arabic) layouts, date and currency formats |
| Interactions | What happens on tap, swipe, keyboard shortcuts, focus order |
Responsive behaviour
Show how layouts adapt — don't make developers guess what happens between your frames.
- Provide key breakpoints (e.g. mobile 375, tablet 768, desktop 1440).
- Use constraints and auto layout to show what stretches, wraps or stays fixed.
- Annotate behaviour that isn't visible: "Sidebar collapses into a drawer below 1024px", "Cards wrap to 1 per row under 640px".
- Define max widths for content and images.
Annotations and specs
Tools like Figma Dev Mode show measurements, colours, typography and generated code for any element. Annotations fill in what inspection can't show: behaviour, logic and intent.
- Annotate interactions, conditional logic, validation rules and data sources.
- Specify animations with property, duration and easing (e.g. "Sheet: translateY, 240ms, ease-out").
- Link to the user flow so developers see how screens connect.
- Note accessibility details: labels for icon buttons, heading levels, focus order, announcements.
① Search — debounce 300ms; min 2 characters; results ordered by relevance.
② Filters — multi-select; selected chips move first; "Clear all" appears when ≥ 1 selected.
③ Empty state — "No results for '{query}'" + Clear filters button.
④ Price — tabular numbers; show original price struck through when discounted.
⑤ Focus order — Search → Filters → Results → Pagination.
⑥ Analytics — fire "search_submitted" with query length and filter count.Assets
- Icons: use the shared icon library or export SVG.
- Images: provide originals or export at the right sizes; prefer WebP/AVIF for photos.
- Illustrations: SVG where possible; Lottie or Rive files for animations.
- Fonts: confirm names, weights and licences.
- Mark exportable layers in Figma so developers can download them directly.
The handoff meeting and design QA
- 1Kick-off: walk developers through the flow, the goals and the tricky parts. Answer questions early.
- 2Agree on scope: what's in this release, what's later, and what can be simplified if time is short.
- 3Stay available: answer questions during the build in a shared channel or comments.
- 4Review early builds: look at work in progress, not just the final version.
- 5Design QA: before release, compare the build with the design on real devices — spacing, typography, states, responsiveness, accessibility, motion.
- 6Log issues clearly: screenshot of the build vs the design, what's wrong, and its priority.
Do
- Involve developers from the first sketches.
- Use components, variables and auto layout.
- Design empty, loading and error states.
- Annotate behaviour and accessibility.
Don't
- Hand over only the happy path.
- Leave multiple conflicting versions in the file.
- Rely on Dev Mode alone to explain intent.
- Disappear after handoff.
Developers are your best design critics for feasibility. A five-minute conversation before handoff can save days of rework after it.
Key takeaways
- Handoff is a collaboration, not a single moment — involve developers early and stay involved.
- Organise files with clear pages, names and a single source of truth.
- Use components, variables and auto layout so designs map directly to code.
- Design every state, edge case, breakpoint and localisation scenario.
- Annotate behaviour and accessibility, prepare assets, and run design QA before release.
Exercise
Prepare a screen for handoff
- Take a screen you designed earlier.
- Replace raw values with components and variables.
- Add empty, loading and error states, and a long-content version.
- Add mobile and desktop versions with responsive annotations.
- Write at least five numbered annotations covering behaviour and accessibility.
Test yourself
Design handoff quiz
5 questions. Score 70% or more to complete the lesson.
