Why you should click through your app before anyone builds it

What a clickable prototype is, why it is the cheapest place to make mistakes, and how to use one with customers and investors before you pay for code.

Product design2 min read

The short answer

Because changing a design costs hours and changing a finished app costs weeks. A clickable prototype looks and feels like the real thing on your phone, but nothing is built behind it. You can show it to customers and investors, find out what confuses them, and change your mind while it is still cheap.

What is a clickable prototype?

A set of designed screens linked together, so tapping a button takes you to the next screen just as the finished app would. It looks real, but there is no code or data behind it.

It sits between a sketch and the real product. Detailed enough that people react to it honestly, quick enough to change in an afternoon.

Why not go straight to building?

Most expensive mistakes in software are not bugs. They are features nobody needed, steps nobody understood, and screens built for a customer who does not exist. Every one of those is cheaper to find in a prototype.

It also gets everyone agreeing on the same thing. Words like simple and quick mean something different to everyone. A screen you can tap does not.

How do you test one with real people?

You do not need a lab. Five people from the right audience will find most of the problems.

  • Give them a task, like booking a trip or reordering a product
  • Watch, and do not help
  • Note every place they hesitate or tap the wrong thing
  • Ask what they expected to happen
  • Fix the worst problem, then try again

Can you raise money on a prototype?

It helps. Investors see a lot of decks. A product they can hold and tap through shows them you have thought it through, and makes the idea far easier to remember after the meeting.

Questions people also ask

What tools are used to make a prototype?
Most are made in Figma, which lets you design the screens and link them together so they can be tapped through on a phone or a laptop.
Does the prototype become the real app?
No, but the designs do. Once agreed, they become the blueprint the engineers build from, which saves time and arguments later.
How detailed should a prototype be?
Detailed enough to test the main journey your customers take. Leave the settings pages and edge cases for later.

Tell us what you're building.

A few lines is plenty. You don't need a spec, and a person will write back.

or email admin@bedrockbytes.com