IT Glossary
What is a wireframe?
The architect’s sketch of a screen: which elements exist and where they sit, in plain lines, with structure decided before aesthetics.
Before a screen can be beautiful it has to be correct, and the wireframe is the instrument enforcing that order. It is the simplified sketch of an interface, drawn in lines, rectangles and placeholder text with no colours, typefaces or photographs, answering the structural questions: which elements the screen contains, in what hierarchy, what sits at the top and what disappears, and how a user flows towards the action. The visual poverty is the method rather than an omission. Faced with a black-and-white sketch, discussion stays on structure — the price is missing, the main action is buried, this step is unnecessary — which is precisely the valuable conversation to have early. Present the same group with a polished design and the feedback slides irresistibly towards shades of blue and opinions about photography, while the structural problems pass unnoticed under the varnish. Its place in the chain is clean: the wireframe for structure, then a visual mockup dressing the approved structure, then an interactive prototype to test on real people, then development — each stage making change more expensive, so each approval belongs at its own level.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247
Why it matters for your business
Structure corrected while it costs a minute
Moving a block or removing a step on a sketch is free; the same corrections on a finished design or inside code cost days and a certain amount of pride.
Feedback on substance, not taste
Black and white keeps the early discussion on what matters — hierarchy, content, flows — rather than on the shades that have their proper turn later.
A shared language between business and team
A sketch everybody understands aligns your vision with their implementation before any cost is incurred, including when you draw it yourself on paper.
Frequently asked questions
What feedback is useful on a wireframe, and what should wait?
Now, the structural questions: are the information and actions that matter to the business present, does the hierarchy reflect real priorities, does the flow contain unnecessary or missing steps, and is any screen or state absent, such as what a user sees on an error or an empty list. Later, on the visual design: colours, typefaces, imagery, tone. Saying you dislike how it looks at wireframe stage is like rejecting an architectural plan over the colour of the drawing.
Wireframe, mockup, prototype — a short recap of the differences?
Three answers to three questions. The wireframe answers what and where, as a black-and-white structural sketch. The mockup answers how it looks, as finished static visual design applied to the approved structure. The prototype answers how it flows, with screens linked interactively and navigable for testing on users before development starts. On small projects the stages compress, but the questions stay the same and stay in that order.
Small project, small budget — can we skip wireframes?
You can skip the formal deliverable sometimes; you cannot skip the stage. At any size, structure gets decided before aesthetics, even if the wireframe is an hour’s sketch on a whiteboard photographed at the end of a meeting. The real cost of skipping shows up statistically in rework, since a finished design rejected for structural reasons is paid for twice. One honest nuance: on template-based sites the proven template is itself a market-validated wireframe, so the discussion legitimately moves to choosing and adapting it.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247