Mockup
A mockup depicts an interface’s proposed appearance and content so people can review visual decisions without a working implementation.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/mockup/
01What it means
A mockup is a representation of how a product or screen should look, often showing typography, spacing, colors, imagery, and realistic content. In digital-product work it commonly presents a static state. A prototype adds simulated behavior for a learning question; visual polish alone does not make a mockup interactive.[1][2]
02Why it matters
Mockups expose conflicts between hierarchy, brand expression, content density, and component consistency. They give designers and engineers a concrete basis for discussing what should appear, while making missing states visible before implementation.
03When to use it
Use mockups to compare visual directions, review responsive layouts, and communicate a proposed screen state. Use an interactive prototype when the question involves navigation, feedback timing, or successful task completion.
04How it works
- Define the visual decision and the audience for the review.
- Use representative content and existing components where appropriate.
- Prepare the relevant viewport sizes and loading, empty, error, or success states.
- Annotate behavior that a static image cannot communicate.
- Review against the task and design principles, then carry decisions into implementation or a prototype.
05A practical example
A reporting team mocks up a dashboard using long customer names and realistic negative values. At a narrow viewport, the table headings become ambiguous. The team changes the hierarchy and documents a compact layout before engineers build the table.
06Where it breaks
A picture cannot demonstrate keyboard interaction, dynamic resizing, latency, or assistive-technology behavior. Attractive presentation can make an unresolved idea appear finished. A mockup should state which decisions are proposals and which constraints have been checked.
Common mistakes
- Approving appearance as evidence of usability.
- Showing only a populated desktop screen.
- Leaving developers to infer behavior from pixels.