Foldwren

Wireframes, mockups and prototypes explained

What wireframes, mockups and prototypes are each for in a website project, and the kind of feedback that is most useful at every stage.

Think of building a house. A wireframe is the floor plan. A mockup is the artist's impression showing colours and finishes. A prototype is a display home you can walk through. Each one exists to settle a different set of decisions, and knowing which you are looking at tells you what kind of feedback will help.

Wireframes: where things go

A wireframe is a plain, usually grey outline of a page. Boxes stand in for images. Lines or rough text stand in for words. There are no colours, no fonts and no photos. It looks unfinished on purpose.

Leaving out the visual detail keeps everyone focused on structure:

  • What is on this page, and what isn't?
  • What comes first, second and third?
  • Where is the main action?
  • How do the pages connect?

Useful feedback at this stage:

  • "Pricing should come before the gallery. It's the first thing customers ask."
  • "There's nowhere for our licence details."
  • "The main button should be 'Book online', not 'Contact us'."
  • "We need a section for the two locations."

Feedback to hold for later:

  • "It looks a bit grey and boring."
  • "I don't like that font."

None of that has been designed yet. The grey is deliberate.

This is the cheapest moment to change your mind. Moving a section in a wireframe takes minutes. Moving it after the site has been designed and built takes hours. So look hard at the order and the content now, and check the phone layout as well as the desktop one.

Mockups: what it looks like

A mockup is a detailed picture of the finished design. It has your colours, fonts, logo, real or near final photos and ideally your actual wording. It is still a static image. Nothing can be clicked.

The mockup answers a different question: does this look and feel like our business?

Useful feedback at this stage:

  • "The green feels brighter than our signage."
  • "This text is hard to read on my phone."
  • "The photos feel too corporate for a family business."
  • "The headline doesn't sound like us."
  • "The button doesn't stand out enough from the background."

Less useful at this stage:

  • "Can we move the services section above the introduction?" That was the wireframe's job. It can still be done, but it now means redoing finished work.

A practical tip. Ask to see mockups with real content in them. A design filled with placeholder text and perfect stock photos always looks tidy. The true test is how it copes with your longest service name and your real photographs.

Prototypes: how it works

A prototype is a clickable version. It might be a set of linked mockups, or an early build of the real site. You can tap the menu, move between pages and get a sense of the flow.

The question it answers is: can people use this?

Useful feedback at this stage:

  • "I couldn't work out how to get back to the services list."
  • "The menu on my phone is fiddly to close."
  • "After I tapped 'Book', I wasn't sure what to do next."

The most valuable thing you can do with a prototype is hand it to someone who hasn't seen it. A staff member, a friend, a loyal customer. Ask them to complete a task, such as finding the price of a service or making a booking, and watch quietly. Where they hesitate is where the design needs work.

Why the order matters

The stages run from cheap to change to expensive to change. That is the reason for the sequence.

  1. Wireframe. Decide structure and content while changes are almost free.
  2. Mockup. Decide the look once the structure is settled.
  3. Prototype or build. Check behaviour once both are agreed.

Problems come from deciding things out of order. If you approve a wireframe without really looking, then ask for a new structure at the mockup stage, the visual design has to be redone. If you restructure after the build, everything does.

This is why designers ask for sign off at each stage. It can seem like bureaucracy. It is really a moment to confirm that everyone agrees before the costly work begins. If you are unsure about something, say so before signing off, because that is when your doubt is cheapest to resolve.

Not every project uses all three

On a small site, running all three stages for every page would be overkill, and a good designer will scale the process to fit.

Common variations:

  • Wireframes for key pages only. The homepage and one service page, with the rest following the same pattern.
  • One mockup to set the style, then straight to building the remaining pages.
  • Designing in the browser. The designer builds a working draft of the real site, which serves as mockup and prototype in one. It shows you how the site truly behaves on your own phone.

Questions to ask at the start

Before a project begins, ask your designer:

  • What stages will I see, and in what order?
  • What am I approving at each one?
  • How many rounds of changes are included per stage?
  • Will I see the phone version at every stage?
  • Will my real content be used, and when do you need it?
  • What happens if I want a structural change after sign off?

And when something arrives for review, start by asking one question of your own: what decision is this meant to help us make? Keep your feedback to that decision, and the project will move faster with fewer surprises at the end.

Your order