Skip to content
GOGodswill
All posts
1 min read

Figma to production: turning designs into responsive UI

How I translate a static design into components that hold up across screen sizes — without pixel-pushing every frame.

  • Frontend
  • Workflow
  • Design

A Figma frame is one width. Your users have dozens. The job isn't to reproduce the mock — it's to infer the system behind it and rebuild that system in code.

Read the design for rules, not pixels

  • What's the spacing rhythm? Repeating values (16, 24, 32) become a scale you reuse everywhere.
  • Where does hierarchy come from — size, weight, colour, or spacing?
  • Which elements are repeated? Those are your components, immediately.
  • What changes between variants? That's your props.

Translate constraints, not absolute positions

Absolute coordinates in a design are a trap. Convert them to relationships: this column is twice that one, that gap is fixed while the content grows, this block is centred within the container.

<section className="grid gap-8 sm:grid-cols-[2fr_1fr]">
  <Hero />
  <aside className="rounded-2xl border p-6">…</aside>
</section>

Build the smallest reusable piece first

Start with the button, the tag, the card — the primitives every screen repeats. Once those exist, pages become composition instead of CSS authoring, and consistency comes for free.

Name things by role

ProjectCard, not GreyBox. SectionHeading, not Title2. Role-based names survive redesigns; positional names break the moment the layout changes.

Close the loop with QA

  1. 1.Compare at the design width first — get the reference frame right.
  2. 2.Then test at 320, 768 and 1280. Designers rarely specify these; your users live there.
  3. 3.Check states the mock doesn't show: hover, focus, loading, empty, error, long text.
  4. 4.Fix contrast and focus rings while you're in there — they're cheap now and expensive later.
The design file is a sample of the system. Your job is to rebuild the system, not the sample.

In short

Extract the rules, translate relationships instead of coordinates, build components by role, and verify states the mock never showed. That's how a static frame becomes an interface that holds up in production.

Let's build together

Have a product that needs building?

I'm available for frontend and mobile app engineering — full-time product roles, contracts, or ambitious freelance builds.