JOURNAL — 015 · Design

Figma to Code: A Handoff Process Developers Don't Hate

Mahnoor Qureshi, Head of Design June 16, 2026 4 min read
Figma to Code: A Handoff Process Developers Don't Hate — journal featured image

Pixel-pushing the file isn't the job. Annotation, tokens, edge cases and empty states — the developer contract that makes builds match designs.

Nothing poisons a project like 'the developer didn't follow the design' — said about a file with no empty states, no error states and four mystery greys. Handoff quality is empathy delivered as documentation: named tokens not hex soup, real content in every state, behaviour annotated at the frame, and a loom walkthrough of the risky interactions.

Hierarchy is the product

Every page secretly asks the user to do one thing next. Design's job is making that next thing obvious to a tired stranger holding a phone in bad light. Everything else is garnish with ambition.

We audit hierarchy with the squint test and the five-second test, not with debates: what reads first, second, third — and does that order match the business's priority list.

When everything shouts, the user leaves. One voice, clearly louder, converts.

The design QA ritual before handoff

  1. Real content in every state: empty, error, loading, translated-long
  2. Squint test per screen: exactly one obvious next action
  3. Contrast pairs measured, not squinted at
  4. Touch targets verified on the smallest supported device
  5. Every interactive element has hover, focus, active, disabled
  6. Loom walkthrough recorded for anything with motion or state

Delight must earn its budget

Motion, illustration and charm are budget line-items like anything else; they belong exactly where doubt and boredom cost money — onboarding, empty states, waiting moments — and nowhere they're stealing attention from decisions.

The test is whether the delight carries information: progress, confirmation, orientation. Animation that answers a question pays; animation that asks for applause should audition elsewhere.

Charming flows get screenshotted. Clear flows get completed. Ship both, in that weight order.

Design is the cheapest trust you can buy — bought wholesale or at retail.ALIFY design practice

Taste is a process

Beautiful outcomes come from boring loops: references argued over, directions killed early, details iterated after everyone is tired. The myth of the inspired genius mainly produces missed deadlines.

Our reviews run on questions, not moods: does this serve the user's next decision, does hierarchy match importance, would this still work with real ugly content. Opinions survive only if they improve answers.

Accessibility is quality

Teams relegate accessibility to a compliance sweep at the end; that's how you get contrast failures treated as surprises. Baked in from palette day one, AA compliance is just craft.

The work is concrete: text pairs tested against 4.5:1, focus states designed on purpose, hit areas that respect thumbs and Parkinson's alike, reduced-motion variants of every flourish.

One in six users has a disability. A site that excludes them isn't minimal — it's unfinished.

Taste debates end where user questions begin.Studio wall print

Where to start this week

For your next screen, design the empty, error, loading and long-content variants before showing anyone the happy path. Developers build what exists; make it exist.

Then keep it honest with a short list:

  • 'Make it pop' accepted as actionable feedback
  • References from three industries and zero analysis of why
  • Approval by committee poll instead of one accountable owner
  • Put the date on the calendar — playbooks without Fridays are just reading

And when the scope outgrows the spreadsheet, that's precisely what our team is for.

Straight answers

How do you handle feedback rounds?

Two structured revision rounds per milestone with consolidated comments from one decision-maker. Async by default, calls for anything subjective — taste discussions die in email threads.

Can you redesign without us losing brand recognition?

Evolution is our default unless strategy says revolution. Equity audit first: what's recognized and must survive the refresh, then invention everywhere else.

How many design concepts do we get?

One direction, done properly — after a shared strategy phase so the direction isn't a guess. Scattergun concepts look generous and are actually the agency hedging; we'd rather spend those hours making one direction undeniable.

Mahnoor Qureshi
Head of Design · ALIFY

Leads brand and product design at ALIFY. Believes taste is a process, not a gift — and conversion is a design metric.

Start a project

Like how we think?

Imagine what we ship. Intro call + fixed quote in 48 hours.

Cookies, minus the crumbs. We use essential cookies to run this site and optional analytics cookies to improve it — analytics only load after you accept. See our Cookie Policy.