liveBook · Manning

Mockup

A mockup is a visual representation of a product or interface’s intended appearance and structure, typically without full functionality.

How 2 Manning books explain it

Everyday Data Visualization

A visual prototype of a design that represents its intended appearance at a specified level of fidelity.

How it is used
Uses visual prototypes to compare layouts and secure stakeholder approval before development.
How deep it goes
Explains increasing fidelity and effort trade-offs, but stops short of detailed component construction.
Examples
Uses dashboard wireframes, bar graphs, a calendar view, line charts, colors, fonts, and interface controls as examples.
What you can do after
Evaluate layouts and apply an appropriate fidelity level before committing to development.

Read how Everyday Data Visualization explains mockup →

Design for Developers

A mock-up is a static visual representation of a proposed interface appearance used for review and refinement.

How it is used
Uses a static visual design to review interface appearance after wireframing and before development.
How deep it goes
Explains timing, visual decisions, review, revision, and handoff, while stopping short of interactive behavior or implementation detail.
Examples
Uses a travel-agency homepage with destination imagery, trending destinations, group travel, precise measurements, and content hierarchy.
What you can do after
Evaluate and communicate a proposed interface appearance, then guide collaborative implementation and revision.

Read how Design for Developers explains mockup →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.