Designers who ship: closing the gap between design and code
The wall between design and engineering is finally coming down — and the designers crossing it are shipping the best work. A look at the rise of the design engineer.
Daniel Osei
Design Engineer, CodexLab
6 min read
For most of my career, code was a wall. Designers handed work over it and hoped. In 2026, that wall is finally coming down — and the designers crossing it are the ones shipping the best work.
The gap between design and engineering used to be structural. Designers produced static files; engineers interpreted them; something got lost in translation, and the most interesting ideas died as “not feasible.” AI-assisted coding and better design-to-code tooling have made that handoff far more porous.
Prototyping in the real material
There’s a difference between a picture of an interface and the interface. When a designer can stand up a working prototype against real data — even a rough one — the conversation changes. You feel the latency, the empty states, the awkward transition that looked fine in a frame. You design with the grain of the material instead of against it.
A rough prototype against real data surfaces the details a static frame quietly hides.
This is the design engineer’s territory: comfortable enough in code to build the thing, fluent enough in design to know whether it’s right. It’s not about every designer becoming a senior engineer. It’s about closing the loop tightly enough that taste survives the trip to production.
Systems make it possible
None of this scales without a real design system. When components are shared between design and code — same names, same behaviour, same constraints — a designer’s change lands in the product instead of in a redline document. The system is the shared language that lets design and engineering move as one team.
AI handles the scaffolding; the human spends time on the interaction details that make a product feel considered.
AI accelerates the boring parts: scaffolding a component, wiring a state, translating a layout. That frees the human to spend time where judgment actually matters — the interaction details, the edge cases, the moments that make a product feel considered.
The goal was never for designers to write more code. It was for fewer good ideas to die in translation.
How we work
Our designers prototype in the browser, our engineers care about craft, and the design system sits between them as a contract both sides trust. Reviews happen on real builds, not just in a design tool. The result is fewer surprises at the end and more of the original intent surviving to launch.
Shipping is a design skill now. The teams that internalise that will keep outrunning the ones still throwing work over the wall.
Daniel Osei
Design Engineer, CodexLab
Daniel works between design and code, prototyping in the browser and shipping the details most people never notice.
On 28 June 2025, accessibility stopped being a best practice for much of the digital economy and became a legal requirement. The EAA’s reach extends well beyond Europe — and so should your response.
AI has gone from autocomplete to collaborator. Here’s how agentic tools are reshaping the way a studio researches, explores, and ships — and why a designer’s judgment matters more than ever.
A static interface assumes every user wants the same screen. Generative UI starts from the opposite premise — and quietly moves the designer’s job from drawing screens to defining the rules that build them.