# Wireframes and Prototypes

> How a design goes from rough to real. Plain plans, still pictures, models you can click or tap on paper, and how much finish each one needs.

**Course:** [UX Design and Research](https://learn.benibix.com/learn/design-user-experience)  
**Time:** 11 min

**After this lesson you can:**

- Tell a wireframe from a mockup
- Pick a fidelity for each question
- Test with a paper prototype

## How a design goes from rough to real

A design usually passes through three stages before it is built. A wireframe is a plain plan of a screen, in gray boxes and lines. A mockup is a still picture of how it will really look. A prototype is a model people can click. Each answers a different question, at a different cost.

A wireframe shows where things go and nothing else. No colors, no photos, no real fonts. Because it is plain, people talk about the structure, not the shade of blue. A wireframe can be drawn in ten minutes and thrown away without regret.

A mockup adds the real look: colors, images, type and real text. It answers does this look right? It does not click. It is the picture you show when the structure is settled and the question is now about style and brand.

A prototype is a model people can tap or click through. It answers can people use it? It can be rough or polished. A paper prototype is screens drawn on paper. A person taps the paper, and someone swaps in the next page by hand. It sounds silly and works well.

Design fidelity is how close a design is to the real thing. A rough sketch is low. A model that looks and acts almost real is high. Match the level to the question. To test if people find a menu, a rough sketch will do. You do not need a polished app.

Rough work has a hidden plus. People are honest about a sketch, because it looks easy to change. Show them something polished, and they hold back. Or they talk only about colors. Rough work gets you the real views.

The common mistake is to jump to high fidelity too early. A week spent polishing a screen makes the team defend it. Then a test shows the whole flow is wrong, and the polish is wasted. Stay rough until the structure works.

![Three versions of the same phone screen. The wireframe uses grey boxes and lines. The mockup adds real color, images and text. The prototype adds a finger tapping a button and an arrow to the next screen.](https://learn.benibix.com/diagrams/wireframe-mockup-prototype.svg)

## Which one to make

1. **Wireframe.** Make one when the question is what goes on the screen and where.
2. **Mockup.** Make one when the layout is settled and the question is how it should look.
3. **Prototype.** Make one when the question is whether people can finish a task with it.

### Example: A paper prototype for a parking app

A team drew 8 screens of a parking app on paper in one morning. In the afternoon, 5 drivers tapped through them as a designer swapped pages.

Three of the five looked for the price before the map. The team moved the price to the first screen before drawing a single pixel.

**Words in this lesson:** [Wireframe](https://learn.benibix.com/term/design/wireframe), [Mockup](https://learn.benibix.com/term/design/mockup), [Prototype](https://learn.benibix.com/term/design/prototype), [Paper Prototype](https://learn.benibix.com/term/design/paper-prototype), [Design Fidelity](https://learn.benibix.com/term/design/design-fidelity)

> **The one difference.** A wireframe shows where things go, a mockup shows how they look, and a prototype shows whether they work. Only the prototype can be clicked.

**Question:** Why do people give more honest feedback on a rough sketch?

**Answer:** It looks unfinished and easy to change. A polished design looks done, so people hold back. A rough one looks open to change, so they say what they really think.

---

Source: https://learn.benibix.com/learn/design-user-experience/wireframes-and-prototypes
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
