Building apps
What is a prototype?
A prototype is an early, working model of a product built to test an idea, a design, or a technical approach before committing to a full build.
New to Bolt? Sign up free.
Technical definition
In software, a prototype is a partial implementation created to answer a question rather than to serve users. Fidelity ranges from a clickable wireframe with no logic, through a working interface backed by fake data, to a functional slice of the real system.
A prototype is disposable by design. It differs from a minimum viable product, which is a real release for real customers, and from a proof of concept, which tests whether something is technically possible at all.
In plain terms
A prototype is a test version. It exists to answer a question, and once it has, you throw it away.
The question decides how much you build. If you want to know whether people understand a screen, a clickable mockup is enough. If you want to know whether an idea works end to end, it needs to run.
Why it matters
Prototypes make disagreement cheap and specific. Describing an idea in a meeting produces polite agreement, because everyone is imagining a different thing. Handing someone a working version produces real reactions.
For a founder pitching, a working prototype changes the conversation more than any deck. For an agency, it converts scope arguments into decisions about something concrete.
AI building has made the low-fidelity prototype largely obsolete, and that is worth stating plainly. When a real working version takes an afternoon, there is less reason to build a fake one. The risk that comes with that: a prototype that works is easy to mistake for a product. It has no error handling, no security review, and no scale testing.
So decide in advance which one you are making, and say so out loud.
