Skip to main content
GullySystem

Clickable Prototype Creation

Clickable prototype creation links screens together so a person can tap through a whole journey on a phone. Nothing is saved behind them, and no database is involved.

Where a prototype is used

  • Watching a shopkeeper or patient attempt the journey without coaching
  • Showing a partner, a bank or a board the idea instead of describing it
  • Settling an internal disagreement about how a step should work
  • Finding a confusing step while moving it still costs nothing

What a prototype is not

The limits are stated before work starts.

Not a working product

Nothing is saved or calculated. The same demonstration data appears each time the prototype opens, so a tester cannot enter real records or see a live result.

Not the foundation of the build

The prototype is discarded when the build starts. What carries forward is the set of decisions it produced.

Not a substitute for a pilot

Testers may respond kindly while tapping through. Only a live release with real use shows whether people want the product.

Not open to endless change

A few rounds of revision are normal. A long run of versions points to a decision being put off.

Choosing what to link

Not every screen needs a working path. Link only the journey you want to test, such as placing an order, and leave settings, profile pages and rarely used menus as plain pictures or leave them out. A narrow prototype gives cleaner findings because testers cannot wander into corners nobody designed. It is also quicker to change between rounds.

Running a test session

Hand the tester the phone, name the task and leave the screens unexplained, because an explanation removes the finding that the session exists to produce. Watch where the thumb hesitates. Note any question asked aloud. A handful of sessions run this way show more than a meeting where everyone agrees politely.

Setting up a fair test

Small choices in the setup change what you learn.

Hide the hints

Prototyping tools can flash the tappable areas on every screen. Turn that off for test sessions, otherwise the tester is shown where to press and the real navigation is never examined.

Pick testers who match

Recruit people who resemble the actual users, such as a clinic receptionist for a booking tool. A colleague from another department will not hit the same doubts.

Write the task first

Each session starts from a concrete task, for example sign up as a new customer and place a first order. Vague prompts like have a look around produce vague findings.

Try the link yourself

Open the shared link on a phone before every session. Broken hotspots and missing screens are far cheaper to find alone than in front of a guest.

What a prototype engagement hands over

  • A link that opens on any phone, with nothing to install
  • The screens in the order a real user meets them
  • Notes from each session, against the screen where it happened
  • A short record of what changed between rounds

A prototype session from setup to feedback

A prototype is judged in a room with a real person holding a phone. The day follows a simple order of preparing the link, watching the tap-through and writing up what was seen. Each step has its own owner. Roles are clear.

Designer before the session

The designer checks that every tap on the first journey lands on a screen. Dead ends are fixed. A short script of tasks is printed, so each tester hears the same words. Nobody gets lost halfway through.

Founder watching quietly

The founder sits beside the tester and says nothing. Hesitations are noted by screen name. When the tester asks what a button does, that question goes on the list as a finding. Silence is the hardest part.

Tester on the phone

The tester is handed the phone and one task, such as booking a slot or placing an order. They talk aloud while tapping. Their confusion points to the screen that needs rework. Mistakes belong to the design, not the tester.

Designer after the last tester

The designer groups the notes by screen. Repeated confusion rises to the top. The next version of the prototype fixes those screens first, and leaves the single odd remark for later. Patterns matter more than single remarks.

Decisions before the first screens are linked

Linking screens forces choices that stay hidden in a slide deck. A founder settles a few of them now so that testers meet a believable journey. Each choice is cheap to make on paper and costly to reverse later. Pencil is enough.

Which journey is tested

Pick one journey that carries the idea, such as sign-up to first order. Link only those screens. A prototype that tries to show everything tests nothing properly. Anything else waits for a later round of testing.

What the fake data says

Agree the names, prices and dates shown on screen. Realistic content makes testers react honestly. Obvious placeholder text invites them to treat the whole thing as a toy. Use real item names and plausible prices.

Who the testers are

Decide who is invited and who is excluded. Friends and relatives soften their comments. People from the real market tell the truth, so list five of them before building starts. Ask each one to bring no help.

How feedback is recorded

Choose one place where notes go and one person who writes them. Scattered notes get lost. A shared sheet with screen, remark and tester name keeps every comment tied to its source. Nothing relies on someone’s memory.

Make an informed decision

Questions to settle before rollout.

Use a representative scenario to decide what this part of the system must show and where review is still needed.

Clickable Prototype Creation

Can someone correct a mistake without losing their earlier work?

Use “Clickable Prototype Creation” to test an incomplete submission with keyboard-only input. Check the error wording and retained values before signing off the screen.

Background reading: W3C: usable form validation

FAQ

Frequently asked questions

How does clickable prototype creation differ from wireframing?

Wireframes are drawings that show structure. The prototype links those screens so a person can move through them on a phone. Projects can use both, and the prototype is the version shown to users.

Can the prototype become the real application?

No. Prototyping tools produce the appearance of an application and not working software, so the build starts separately. Screen structure, wording and testing decisions carry across. Nothing else does.

Will testers think it is real?

They may. Testers are told that nothing is saved, so they do not enter real details or expect a reply. Anyone shown it outside your company gets the same note in writing.

How many people should try the prototype?

Nielsen Norman Group suggests no more than five users per study, and a small round like that surfaces the main stumbling blocks. If you serve very different groups, such as shop owners and their customers, test each group separately.

Do we need a polished look for the prototype?

Not at first. Plain screens are enough when the question is whether people understand the steps. Visual polish matters later, when the question becomes whether the product feels trustworthy.

Which tool is used to build the prototype?

A design tool such as Figma is the common choice, and it produces a link that opens on a phone. The tool matters less than the task you give testers and the notes you take.

Talk to us

Tell us what you need.

Tell us what your team does today, where work gets stuck and what you want to change.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements