101Turn
Insights
Design3 min read

Designing for Developers: How to hand off UI without losing your mind

Designs look perfect in Figma but broken in the browser. This is exactly how we hand off design to developers so the final product actually matches the mockup.

By the 101Turn studio
Designing for Developers: How to hand off UI without losing your mind
In this article
  1. The states nobody designed
  2. Spacing that means something, not spacing that looks right
  3. Responsive behaviour is a design decision, not an implementation detail
  4. Naming things so a developer doesn't have to guess
  5. Why this works better as one team, not two companies

Ask any developer where a project actually slows down and the answer is rarely "the coding". It's the handoff. That's when a beautiful Figma file has to become a real, working interface, and half of what the design implied never made it into the file.

A hand with a pen over a notebook at a dim desk.
Photo: Amr Taha, Unsplash

The states nobody designed

A screen in Figma usually shows one moment: the happy path, populated with clean sample data. A real screen has to handle a dozen other moments too. Loading, empty, one item, a hundred items, an error, a name too long to fit, or someone on a slow connection halfway through a request. If those states aren't designed, the developer designs them by default, under deadline, and the result rarely matches what the designer would have chosen.

The fix isn't designing every state in full detail. It's naming them explicitly, even as a short note: what should this screen show when the list is empty? What happens if this fails?

Spacing that means something, not spacing that looks right

A design file where every gap is eyeballed to "whatever looked right" produces a system a developer can't extend. A design file built on a real spacing scale, a fixed set of steps like 4, 8, 12, 16, 24 and 32, lets a developer build parts that stay consistent without extra effort, because the numbers repeat on purpose.

This is invisible to a client looking at the design, and it's the difference between a screen that stays tidy as new features get added and one that slowly drifts.

Responsive behaviour is a design decision, not an implementation detail

A design file usually shows one screen width. What happens between that and a phone is often left for the developer to improvise. Under deadline, that usually means "just make it smaller", which rarely reads well on a narrow screen.

Deciding, even briefly, what should stack, what should hide and what should resize at each screen width turns a guess into a decision. It's far cheaper to make that decision once in the design file than to redo it three times in code.

Handoff breaking down between design and dev?

Naming things so a developer doesn't have to guess

A layer named "Rectangle 47" tells a developer nothing. A layer named "card-hover-state" tells them exactly what it is and when it applies. This sounds small, but across a hundred layers in a real product it's the difference between a handoff that takes an afternoon and one that takes a week of questions.

The same goes for components. A button designed once and reused is one piece of work for the developer. A button redrawn slightly differently on twelve screens is twelve near-identical pieces, and hoping nobody notices they don't quite match.

Why this works better as one team, not two companies

Every one of these problems gets smaller when the same people who designed the screen are the ones who build it, because there's no file to interpret - there's a conversation. A question that would be a day-long email thread between a design agency and a dev shop is a five-minute conversation across a desk. That's not a nicety; it's the actual reason project timelines slip as often as they do, and it's avoidable by structure, not by better documentation.

Related on this site
Topics

Share

Written by the 101Turn studio

A small studio in Ahmedabad, India building apps, websites and SaaS products. If this touched something you are working on, we reply within one working day.

Message on WhatsApp

Want design and build under one roof?

Related reading
Get in touch

Talk to the people who’d build it.

Tell us what you're working on and what's slowing you down. A short call is usually enough to know whether we're the right fit - no proposal required first.

Quick links

WhatsApp