Review: design handoff tools developers actually open

Software Reviews · 2026-01-16 · 7 min read

By Arjun Mehta, Engineering & product

Handoff is a communication problem wearing a software costume. Some tools help; most add a second place to look.

Every handoff tool promises to end the back and forth between design and engineering. In practice the back and forth is caused by unstated decisions — what happens on error, what the empty state says, how this behaves at 320 pixels — and no exporter fixes that.

The tools that helped shared one property: they lived where the work already happened. A tool requiring a separate login and a separate URL got checked at the start of a ticket and never again, so it was stale within days.

Token export was the genuinely useful feature. Colours, spacing and type scales pulled straight into code removed a whole class of small mismatches and, more importantly, made the design file authoritative rather than advisory.

Generated code remains a trap. It produces markup shaped like a picture rather than a component, and reviewing it takes longer than writing the real thing.

The cheapest improvement we found cost nothing: a short annotation on every screen covering loading, empty, error and the narrowest breakpoint. Teams that adopted that convention stopped caring which tool they used.

Tags: design, tooling, review

Arjun Mehta — Arjun writes about web performance, developer tooling and applied AI for ESPYCRUX. He has spent the last decade building and maintaining production web apps, and most of his articles start from something that broke in one of them.