Talk to a person. We reply within one working day.

SEO and AI search
Web
AI
Resources
WorkAboutStart a project

Before you build · 21 Nov 2026 · 5 min read

App prototype: how to test a clickable mockup before building

A prototype lets you find out whether people understand your app before anyone writes the real code. It is the cheapest test you can run.

The short answer

A mockup is a static picture of a screen, while an app prototype is a set of linked screens you can tap through. A clickable mockup is a simple prototype. Test it with about five people from your audience, watch where they hesitate, and change the flow before development begins.

Mockup, wireframe and prototype: what each one is

These three words are used loosely, and the confusion costs time in meetings. Here is a clear way to use them.

  • A wireframe is a rough layout of a screen in plain boxes and labels. It shows where things go, with no colour or final text.
  • A mockup is a polished picture of a screen, with real colours, fonts and images. It shows how the app will look, but you cannot tap it.
  • An app prototype links screens together so a person can move through them as if the app worked. A clickable mockup is a prototype built from designed screens, where taps jump to the next screen.

So the difference between a mockup and a prototype is movement. A mockup answers "does this look right?" A prototype answers "can a person do the task?" For testing an idea, the second question matters more. Design tools can produce both, and the choice of tool is less important than the questions you ask with it.

Why test before you build

Changing a screen in a design file takes minutes. Changing the same screen after it has been built, tested and connected to a server takes days. Problems found at the prototype stage are the cheapest to fix, and some, such as a flow that nobody understands, can save the whole project.

A prototype also helps you avoid building features nobody uses. Our guide on what to build in the first version of your app explains how to choose, and a prototype gives you real evidence for the choices. When you work with a team, a tested prototype also makes quotes more reliable, because the scope is visible. The mobile app development service page describes how design and testing fit into a project.

What to decide before you make one

A prototype with no purpose produces vague feedback. Write down what you want to learn.

  1. Pick one to three key tasks: sign up, find a product, book a slot, pay. These become the test.
  2. Decide the success measure for each: can the person complete it without help, and how long do they hesitate?
  3. List the screens needed for those tasks only. Skip the rest.
  4. Write realistic content. Placeholder text such as "Lorem ipsum" hides problems with length and meaning.
  5. Decide which device size you are showing, and test on a real handset where possible.

Keep it small. A prototype of ten well-chosen screens can teach you more than one of fifty. Basic ideas of layout and navigation are covered in app UX basics for first-time founders.

How many people should test it

For finding the main problems, a small number of people is enough. A common rule among usability practitioners is that a handful of testers, around five, will reveal most of the big issues in a flow, and that several small rounds beat one large one. It is a rule of thumb, not a law, so treat it as a guide.

Choose people who resemble your real users, not friends who will be polite. If your app serves two different groups, such as customers and staff, test a few of each. Run a first round, fix what you found, then run a second round on the improved version. If the same problems no longer appear, you are ready to move on.

A larger survey can come later, and it measures a different thing. Prototype testing finds out why people struggle. It does not tell you how many people would buy.

How to run a test session

Before

Explain that you are testing the design, not the person, and that there are no wrong answers. Ask permission if you will record the screen or voice, and say what happens to the recording.

During

Give the person a task in plain words, such as "Find a class on Saturday and book it". Then stay quiet. Ask them to think aloud. Do not explain the screen or rescue them when they stall, because the stall is the finding. Note where they hesitate, tap the wrong thing, or say they are confused.

After

Ask open questions: what did you expect to happen, what was unclear, what would you change. Thank them. Write notes straight away, while you remember, and mark each problem with how many people met it.

You can run sessions in person or remotely over a video call with screen sharing. Remote sessions reach more people, while in-person sessions let you see hand movements and hesitation more clearly.

What to change before building

Sort what you heard into groups.

  • Problems that stopped someone completing a task. Fix these first.
  • Problems that slowed people down or caused doubt. Fix the ones that several testers met.
  • Wording that was misread. Change the words and test again.
  • Requests for new features. Note them, but do not add them straight away. One person's wish is not a requirement.

Watch what people did as well as what they said. People often say a screen is fine and then fail to use it. Update the prototype, retest the changed parts, and then freeze it as the reference for development. Keep a note of decisions you made and the reasons, so the team does not reopen them later.

Tools and effort

You do not need special skills for a first prototype. Many design tools let you draw screens and draw a link from a button to the next screen, and some can run the result on a real handset. Paper sketches also work for the earliest ideas: lay the pages out and swap them by hand as the person points. Choose the lightest method that answers your question, and move to a more polished version only when the flow is settled.

What a prototype cannot tell you

A clickable mockup does not show speed, battery use, behaviour with a poor connection or how the app copes with real data. It cannot prove that the store will approve the idea, though reading the guidelines early helps, and our article on app store rejection lists common issues worth checking against your design. Real testing on a built version comes later, as set out in how to test a mobile app before launch.

It is also worth checking the practical side while the design is cheap to change: is the name free, are the handles and domain available, and does the name clash with another product? See checking a brand name, domain, handles and conflicts. If the name has to change, a prototype is the easiest time to do it.

Related guides

Questions and answers

What is the difference between a mockup and a prototype?

A mockup is a static, finished-looking picture of a screen. A prototype links screens so a person can tap through a task. A clickable mockup is a prototype made from designed screens. Mockups test appearance, while prototypes test whether people can complete tasks.

How many people should test an app prototype?

Around five people from your real audience will reveal most major problems in a flow. Run a small round, fix what you found, then run another. It is a rule of thumb, so test each separate user group you serve.

What should I change before building the app?

Fix problems that stopped people completing a task first, then ones several testers met, and reword anything misread. Record feature requests but do not add them on one person's word. Then freeze the prototype as the reference for development.

Do I need a finished design to make a prototype?

No. You can link wireframes into a rough prototype to test the flow before spending time on visual design. Use real wording, since placeholder text hides length and meaning problems.

Can a prototype replace testing the real app?

No. It cannot show speed, battery use, behaviour on a poor connection or how the app handles real data. Test the built app on real devices as well before launch.

Tell us what you are building.

A short call, a written plan and a fixed quote. No obligation.

Get a free quote