Methods

Clickable prototype vs. mockup: which proves demand?

A mockup shows people what something could look like. A clickable prototype lets them use it. Only one of those produces evidence you can trust.

Guide · 5 min read

Definitions, without the jargon

• Mockup: a static, high-fidelity picture of a screen. It communicates layout and style, but nothing happens when you click.
• Clickable prototype: an interactive version of the core workflow. Buttons respond, screens advance, and a person can complete a realistic task end to end.

The difference that matters: opinions vs. behavior

When you show someone a mockup, you get an opinion: "looks nice." When you hand someone a clickable prototype and ask them to complete a task, you get behavior: where they hesitate, what they misunderstand, and whether they reach the outcome at all. Behavior is the evidence that actually validates an idea; opinions are noise.

People are unreliable narrators of their own future behavior. They will tell you they would use something, then never click. A prototype catches that gap before you fund a build.

When a mockup is enough

• You are testing visual direction or branding, not whether the workflow works.
• You need an asset for a pitch deck or stakeholder alignment.
• The core interaction is already proven and you are refining look and feel.

When you need a clickable prototype

• The riskiest question is "will anyone actually do this," not "does it look good."
• The value lives in a flow — multiple steps, decisions, or states.
• You are about to spend real money and want evidence before committing.

You do not need a full build to get a prototype

A clickable prototype sits deliberately between a mockup and a production app. It feels real but skips authentication, payments, and data plumbing, which is why it should cost far less than a production MVP. The goal is evidence, not infrastructure.

← Back to Promptlaiy