A wireframe is a simple, low-detail layout of a screen that shows where content and controls go, without final colours, images or styling.
Design · Reviewed by Ray Rasouli
Ask about wireframe
Plain answers, with your setup in mind.
Ask anything about wireframe. For example, how it works in your current tools.
A scripted guide for now. It does not store what you type.
A wireframe is a blueprint for a screen. It uses plain boxes, lines and placeholder text to show structure: what goes at the top, where the main action sits, what information appears in which order.
Before building a new returns page for a retailer's website, a designer might sketch three wireframes and walk the customer service team through them. Moving a box on a wireframe takes seconds; moving a feature after it is coded takes days.
Wireframes keep early conversations focused on content and flow instead of colour preferences.
The usual flow, step by step.
In practice
Stakeholders judge it on looks.
People comment on the grey boxes instead of the structure, missing the point of the exercise.
Real content is not used.
Placeholder text hides the fact that real product names or error messages will not fit.
Edge cases are skipped.
Only the happy path is drawn, so empty states, errors and long lists surprise the build team.
It is treated as final.
Developers build straight from a rough wireframe without the detail or testing it was never meant to carry.
A wireframe shows structure in plain boxes. A mockup adds final visuals such as colours, fonts and images, but usually is not clickable.
Anything from paper and a whiteboard to design tools like Figma or Balsamiq. The tool matters less than getting feedback early.
A 30-minute discovery call with Ray, then a clear list of what to fix first. No obligation.
With Ray Rasouli. No obligation.