Article

August 4, 2026

Why we prototype in production code

Clickable mockups are great for flows. For anything involving data, motion or performance, we prototype in the real stack — and keep what works.

August 4, 2026

Why we prototype in production code

Clickable mockups are great for flows. For anything involving data, motion or performance, we prototype in the real stack — and keep what works.

Article

August 4, 2026

Why we prototype in production code

Clickable mockups are great for flows. For anything involving data, motion or performance, we prototype in the real stack — and keep what works.

Static prototypes lie politely. They never load slowly, never show an empty state and never meet a 400-character customer name.

The first ten percent

For data-heavy products we build the riskiest ten percent in production code during week one. It’s rough, but it’s real — and it answers questions a mockup can’t.

What we keep

Not everything survives. But the data layer, the component boundaries and the performance budget usually do, which saves weeks later in the engagement.

When we don’t

For early concept work and flows with no real data yet, a quick design prototype is still the fastest way to learn.

Tagged

Prototyping, React

Written by

Jonas Lindqvist

Co-founder, Engineering Lead

Jonas has spent fifteen years building front-ends that have to be fast, accessible and maintainable. He reviews every architecture decision the studio makes.

View profile

Field notes, monthly

Get the next essay in your inbox.

One thoughtful email a month. No spam, unsubscribe anytime.

Create a free website with Framer, the website builder loved by startups, designers and agencies.