Insight
The Prototype Forgot It Was a Prototype
A prototype used to look unfinished, with grey boxes, fake names and a link to a design file, and that look told everyone not to ship it. Now a prototype is real code that looks done, so "this is only a test" has to be designed on purpose.
The look did the warning
A wireframe with grey boxes and placeholder names goes up in a review. Comments land on the idea, not the pixels, and the path to release stays closed without anyone saying a word.
The rough look goes away
The same idea is rebuilt in code: grey boxes fill in with real components and real data, and the "draft" feeling drops off. Underneath, what's missing (tests, error states, accessibility) stays invisible, and the path to release opens.
Figma's chief design officer said something at Config India that I keep thinking about. People write 17 times more code than before, she told TechCrunch.
For years the rough look of a prototype did a quiet job. Grey boxes, the same fake name in every row, a design-file link instead of a real URL. Nobody had to say "this isn't real." In the review people talked about the idea, and nobody asked to put it in production, because it obviously wasn't production.
Now we can build the same idea in real code in an afternoon, with real components and real data. It works when you click it. So the teams watching the demo ask a fair question: when can we ship it? What's missing is the part you can't see. No tests, no empty or error states, no accessibility check, edge cases faked to make the demo run. It looks finished, so everyone assumes it is.
We don't miss the grey boxes. We do miss how clearly the prototypes said "not yet."