Term · Web & development
Prototype
A prototype is an interactive model of a website or application that lets people click through screens as if using the real product, before it is developed. It is used to test whether the structure and flows make sense and to align everyone on what will be built.
[ 01 ]
Explained
Types
- Low-fidelity: linked wireframes, focused on structure and flow.
- High-fidelity: designed screens with realistic content and interactions, close to the final look.
- Coded prototypes: working code with limited functionality, used for complex interactions or technical feasibility.
What to test
- Can users complete key tasks without help — booking, ordering, finding information?
- Where do they hesitate or get lost?
- Do stakeholders agree on what the product does?
- Are all states considered: errors, empty screens, loading?
A few test sessions with real users often reveal the most important problems.
Prototype vs MVP
A prototype simulates the product, usually without real data or back-end logic; it tests understanding and usability. An MVP is a working product used by real users; it tests demand.
[ 02 ]
FAQ
Frequently asked questions
How long does a prototype take?
Depending on scope, from days for key flows to weeks for complex applications. It saves more time than it costs by preventing rework.
Can the prototype become the product?
Design prototypes usually cannot; they guide development. Coded prototypes are sometimes extended, but are often rebuilt properly.