Prototype

A prototype is a preliminary version of a product or feature built to test an idea, demonstrate how it will work and gather feedback before committing to full development. It ranges from paper sketches to clickable mockups to working code that handles only a narrow case.

Why it matters

Building the wrong thing is the most expensive mistake in product work. A prototype lets users and stakeholders try a concept early, when changes cost hours rather than weeks. Low-fidelity prototypes check the idea and flow, while high-fidelity ones test details such as wording, animation and layout. A prototype is meant to answer questions and is often discarded, unlike an MVP, which is a real product released to real customers.

Example

1. Sketch 6 screens on paper -> test with 3 users
2. Build clickable screens in a design tool
   linked by buttons -> test with 5 users
3. Code a small working demo of the risky feature
   -> check technical feasibility

Common mistakes

• Polishing it so much that it becomes expensive to throw away.
• Shipping prototype code to production without a rewrite or review.
• Testing without clear questions to answer.
• Using the word interchangeably with MVP or wireframe.

Related

• Wireframe
• MVP
• UX research
• User flow

This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.