←  All terms
P
Design Systems

Prototype

A prototype is an early simplified model used to test ideas, flows, and usability before full implementation.

A prototype is an early simplified model used to test ideas, flows, and usability before full implementation. Value comes from governed tokens, accessible components, clear documentation, and consistent maintenance. The concept is closely related to Wireframe and Web Application.

Read more

Wireframe

Web Application

Low-Code

Design QA

FAQ

Prototype

When is a prototype worth building before development?
A prototype pays off when flows are complex, assumptions untested, or changes after implementation expensive, as with web applications, configurators, and multi-step forms. For a simple content page a wireframe is often enough. A prototype, for example in Figma, moves errors from costly development into the cheaper concept phase.
How realistic should a prototype be?
As realistic as the test question demands. A rough clickable draft is enough to check navigation and flow, while testing animations or form logic needs more detail. Too much polish costs time and steers test participants toward looks instead of flow. The effort should match the risk of the decision.
What is the difference between a wireframe and a prototype?
A wireframe shows structure and content arrangement statically, usually without visual design. A prototype makes flows clickable and tangible, with interactions and often visual design. The wireframe answers what goes where; the prototype answers how using it feels. The prototype often grows out of the wireframe.