# Mockup

A mockup depicts an interface’s proposed appearance and content so people can review visual decisions without a working implementation.

- Type: artifact
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-10-20
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/mockup/>)

## What 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.

## Why 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.

## When 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.

## How it works

1. Define the visual decision and the audience for the review.
2. Use representative content and existing components where appropriate.
3. Prepare the relevant viewport sizes and loading, empty, error, or success states.
4. Annotate behavior that a static image cannot communicate.
5. Review against the task and design principles, then carry decisions into implementation or a prototype.

## A 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.

## Where 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.

## Sources

1. [Mockups](<https://ixdf.org/literature/topics/mockups>) — Interaction Design Foundation · Educational reference
2. [UX Deliverables: Glossary](<https://www.nngroup.com/articles/ux-deliverables-glossary/>) — Nielsen Norman Group · Professional guidance

## Related topics

- [Wireframe](<https://wiki.soroush.uk/topic/wireframe/>)
- [Prototype](<https://wiki.soroush.uk/topic/prototype/>)
- [Design Handoff](<https://wiki.soroush.uk/topic/design-handoff/>)
