Changing a screen in a design file takes minutes. Changing the same screen after it has been built, tested and shipped takes days, and sometimes a rewrite. That difference is the whole argument for prototyping, and it matters most when money and time are short.

A clickable prototype is a set of designed screens linked together so they behave like the real product. You tap a button and the next screen appears. Nothing is stored and nothing is calculated, but to the person holding the phone it feels close enough to react honestly.

Prototype the flow, not the whole product

The temptation is to design everything. Resist it. Pick the one or two flows that decide whether the product works: the first five minutes for a new user, the moment they get the result they came for, or the step where they pay. If people get stuck there, nothing else matters yet.

Twelve screens is often enough to cover a sign-up, a short onboarding and the main action. Keep the screens realistic: real labels, realistic numbers and the actual words you plan to use. Placeholder text hides the problems you are trying to find.

Five people will tell you a lot

You do not need a research lab. Find five people who match your customer, share your screen or hand them your phone, give them a task and stay quiet. "You just signed up. Book your first appointment." Then watch where they hesitate, what they tap first and what they say out loud.

Write down what you see, not what they tell you they would do. People are polite about ideas and honest with their thumbs.

What to look for

  • Where people stop and read twice. That screen is asking for too much.
  • Buttons they look for and cannot find. The label or the position is wrong.
  • Words they use to describe a step that differ from yours. Use theirs.
  • Moments of "oh, nice". That is the part to protect when budgets get cut.

What a prototype will not tell you

It will not tell you whether people will pay, how the product performs with real data, or whether they come back next week. It tests whether the idea is understandable and the flow is usable. For the other questions you need a live product, a waitlist or a pre-sale.

It also helps with investors and developers

A prototype you can hand to an investor says more than a slide that describes the product. And when you do start building, developers work from screens that are already agreed and tested, which cuts down on the back and forth that eats the first months of a build.

Where to start

If you are not sure which flow matters most, start with a User Flow Map: one key flow mapped step by step, with the screens and edge cases named. When the steps are agreed, our Clickable Prototype designs up to twelve screens of one or two flows and links them in Figma, with a short script for running your first tests.