Back to Glossary

Mockup

Synonyms: UI mockup, hi-fi mockup, visual comp, design comp, static design

Do not index

Definition

A mockup is a static, high-fidelity picture of a screen. It shows real colors, fonts, icons, images, and spacing, so the team can judge how the product will look before anyone writes code.
It sits between a wireframe (gray boxes and placeholders) and a prototype (screens you can click through). Mockups exist because people react to visuals much faster than to gray boxes. Clicking one does nothing, which surprises at least one stakeholder per project.
 

Use cases

A weak mockup gets approved in review, then breaks in development once real data shows up.
Examples:
  • The lorem ipsum trap: The mockup shows a 2-word username and a perfect stock photo. Production gets “Christopher Alexander Nguyen-Smith” and a blurry selfie. Text wraps, cards overlap, and the bug ticket lands on the designer.
  • “Can we launch Friday?”: A founder sees a polished mockup and assumes the product is 90% done. Engineering hasn’t started yet. The timeline argument starts in that same meeting.
  • Polishing the wrong page: The team skips straight to hi-fi and spends 2 days on button shades before anyone checks whether users need that page at all.
 

How it's used in practice

  • Start from the approved wireframe: Lock layout and flow first, then add the visual layer.
  • Build from your design system: Use existing components and tokens so developers reuse code that already exists.
  • Test with ugly content: Drop in the longest name, a 3-line headline, an error message, and 0 search results.
  • Cover key breakpoints: Mobile, tablet, and desktop at minimum for anything responsive.
  • Label it before sharing: Write “Static mockup, not interactive” on the frame or in the review invite.
🪄
Design the empty, loading, and error states before the happy path. Real users hit those screens every day, and they're the ones developers end up guessing at during handoff.
 

Challenges & limitations

  • No behavior: A mockup can’t show transitions, hover states, or loading. You need a prototype or written annotations for that.
  • Feedback turns into taste debates: Polished visuals get reviewers arguing about colors and fonts while nobody checks whether the flow works.
  • Gets outdated fast: Once development starts, the mockup and the live product drift apart unless someone owns updating the file.
 

Commonly used tools:

  • Figma: Best for team collaboration, shared libraries, and dev handoff
  • Sketch: Best for Mac-based teams with existing Sketch libraries
  • Penpot: Best for teams that want a free, open-source option
 

Free resources

Share this post

Get free UX resources

Get portfolio templates, list of job boards, UX step-by-step guides, and more.

Download for FREE
 
 

The best email 📮 for growing 🌱 designers

Honest notes about the work behind the work. Read in 2 minutes, weekly. Free forever.
 
 
     
    notion image
    Join 13,045 designers and get tactics, hacks, and tips.