Mockups are static, medium-to-high fidelity visual representations of a user interface used to show layout, content, and look-and-feel before development begins. They sit between low-fidelity wireframes and interactive prototypes, letting teams review and align on a design early.
Mockups
Mockups are static, medium-to-high fidelity visual representations of a user interface, used to communicate layout, content, and look-and-feel before any code is written. They sit between the rough boxes of a wireframe and the clickable behavior of a prototype, giving stakeholders something concrete enough to react to without committing engineering time.
- Visual fidelity - Real colors, typography, spacing, and imagery, so reviewers see close to the intended final design.
- Static by nature - They show a moment in the interface rather than interactive flows, keeping them cheap to produce and change.
- Alignment tool - A shared artifact that gets designers, product, and engineering agreeing before build starts.
- Iteration-friendly - Fast to revise, so ideas can be explored and discarded before they become expensive.
In real API work the same instinct shows up as mock APIs and example-driven design: teams mock an interface — visual or programmatic — so consumers can react to it before it is built, exactly as they would with a UI mockup. Pairing UI mockups with mocked endpoints and OpenAPI contracts lets frontend, backend, and partner teams design in parallel against a shared, disposable picture of the product.