Plan and test an app prototype as a learning instrument rather than a decorative preview.
A prototype is valuable when it changes a decision before expensive implementation. Its fidelity should match the uncertainty: sketches can test structure, clickable flows can test comprehension, coded slices can test interaction or technical feasibility, and service simulations can test operations.
Write the learning question first
State the decision the team will make and the evidence that would change it. Examples include whether users understand a concept, can complete a critical flow, trust a permission request, recover from an error, or whether an integration meets latency and reliability needs.
Define the testable representation
- Target participant, context, device, accessibility, and prior knowledge
- Task trigger and realistic data without exposing sensitive information
- Prototype scope, fidelity, working interactions, and deliberate omissions
- Moderator script, neutral prompts, consent, recording, and observer roles
- Success, hesitation, error, recovery, comprehension, and confidence signals
- Decision rule, owner, deadline, and next experiment
Match fidelity to uncertainty
| Prototype | Answers well | Cannot establish |
|---|---|---|
| Paper or static wireframe | Navigation concepts and terminology | Real interaction timing |
| Clickable visual flow | Sequence, hierarchy, and comprehension | Backend feasibility or production performance |
| Coded vertical slice | Interaction and technical risk | Whole-product market demand |
Run a focused prototype cycle
- Prioritize the highest-cost uncertainty.
- Choose minimum sufficient fidelity.
- Create representative tasks and states.
- Test with relevant people individually.
- Synthesize behavior and root causes.
- Decide, revise, discard, or advance.
Avoid prototype theater
- Showing only the happy path
- Explaining the interface while testing it
- Recruiting teammates who know the design
- Treating visual enthusiasm as willingness to adopt
Keep a decision log
Record question, participants, context, tasks, prototype version, observations, severity, interpretation, confidence, contrary evidence, decision, owner, and next step. Preserve clips or notes only with appropriate consent, access, and retention.