Real data, real devices, real timing. What changes when the first prototype is a working page, and when it isn't worth it.
Real data changes the design
A mock-up with three tidy rows looks finished. The same screen with two hundred real rows, long names and missing values shows what the design really needs.
Real devices, real timing
On a phone, in a browser, with a normal connection, you learn things a static frame cannot show: how fast it feels, how the keyboard covers a field, how a tap target behaves.
Polish comes second
We prototype the structure and behaviour in code first, then polish the visual detail in Figma once the flow is proven. That order avoids polishing screens that later change.
What it costs
Less than people expect when the components are shared, and far less than rebuilding a finished design that did not work.