Start a project

Design in the browser, sooner

Static mock-ups are a great place to think and a poor place to decide. Here is how we move faster.

By PixelMunch Studio

2 min read

Abstract pointillist artwork with warm ember and sand tones

A static design file is a beautiful liar. It shows a page at one width, with perfect content, on a fast machine, frozen in time. Real products are none of those things. They stretch, they load, they fill up with long names and empty states, and they move.

That is why we try to get our ideas into a browser as early as possible, often in the first week of a project.

What the browser tells you that a canvas cannot

  • How type actually renders, wraps and reflows across every width in between your breakpoints.
  • Whether an interaction feels right at real speed, with real latency.
  • How content behaves when it is twice as long, or missing entirely.
  • Whether the layout holds up with a keyboard, a screen reader and zoom at 200 percent.
  • What the experience costs in bytes and milliseconds on an ordinary phone.

Each of these can quietly overturn a decision that looked settled in a mock-up. Finding that out in week two is cheap. Finding it out in week ten is not.

Sketch, then prototype, then build

This does not mean abandoning design tools. We still sketch, explore and present in them, because nothing beats a canvas for thinking broadly. The shift is in where decisions get made. Direction is explored on the canvas. Detail is decided in code.

Explore on the canvas. Decide in the browser.

To make that practical, our designers and engineers share a single source of truth for design tokens: colour, type, spacing, radii and motion. A change to a token in a prototype is the same change in production, so prototypes do not become throwaway work. They become the first draft of the real thing.

Pair, do not hand off

The biggest gains come from people rather than tools. When a designer and an engineer sit with the same prototype and tune it together, a week of back-and-forth collapses into an afternoon. The designer sees constraints as they appear. The engineer sees intent before it is lost in a specification.

The result is not just faster. It is better, because the people who care most about the details are the ones making them, in the medium where they will actually live.

Latest writing