Designing in the browser.

Written by

Sofia Mäkinen
Interface Lead
The browser is where the work ends up. We have started letting it in much earlier.
Static mockups are good at one thing: showing a single screen at a single size on a perfect day. Everything that makes an interface feel right, like motion, loading, long names and slow networks, lives somewhere a mockup cannot reach.
So once the direction is set, we move into code. Layouts are built responsive from the first pass, type is tuned on real devices, and interactions are judged by using them rather than by reading a spec.
A prototype you can break teaches you more than a picture you can only admire.
Design tools still matter for exploring. We sketch, compare and throw away directions there. But the decisions we keep are the ones that survived contact with the browser.
The side effect is a better handover. Engineers receive something that already works, and the conversation moves from what we meant to how to scale it.


