Mockup

Mockups normally show color, typography, imagery and component styling at higher fidelity than wireframes, but may not reproduce full product behavior. In practical terms, Mockup belongs to the structure and interaction layer. Knowing that layer is important because it tells you what the term can change, what it cannot change, and where to look when something behaves unexpectedly.

The common mistake is to use Mockup as if it also meant Prototype. That blurs two separate decisions and usually sends troubleshooting in the wrong direction. A better test is practical: Do not mistake a static mockup for proof that responsive behavior and interaction states work.

In day-to-day work, Mockup matters when the concept needs to be identified precisely instead of being grouped with a nearby term. The practical value is not the vocabulary itself; it is being able to identify the right control, file, setting or decision when the concept becomes relevant.

A high-fidelity mockup can show final typography, imagery, spacing and color for a page without implementing the actual behavior. That example is useful because it turns the definition into something you can recognize, test and discuss with other people working on the same project.

Use these references when you need documentation-level detail, specifications or product-specific behavior beyond the plain-English explanation above.