Prototype

Conversion & UX

Also: High-Fidelity Prototype · Interactive Prototype · Proof of Concept

What it isA clickable draft before real code
Not aFinished product
Best usedBefore development starts
Watch forPolishing too early

Quick definition

A prototype is a working draft of a website, app or product feature used to test how it looks and behaves before it's actually built. It ranges from simple clickable mockups to near-final interactive experiences, and exists to catch problems while changes are still cheap.

How it varies across Australia

Teams that prototype before development typically catch usability problems earlier and spend less time on rework, though the size of that saving varies with project complexity. The benchmark that matters isn't a number, it's whether the prototype gets tested with real users before code gets written.

See conversion and UX benchmarks across Australian industries

What it actually means

A prototype is a rehearsal, not the performance. It lets a team test whether an idea works before anyone writes production code, and it's built specifically to be changed or thrown away.

Prototypes sit on a spectrum. A wireframe is the roughest form, boxes and labels showing layout with no styling. A prototype adds interactivity on top of that, links that click through, buttons that respond, flows a user can actually walk through. A mockup sits somewhere between, showing visual design without full interaction. The further along that spectrum you go, the more it costs to change your mind.

Good prototyping culture treats fidelity as a dial, not a destination. Low-fidelity prototypes are for testing whether the flow makes sense. High-fidelity prototypes are for testing whether the interface communicates trust and clarity. Skipping straight to high fidelity is how teams end up defending pixel choices instead of questioning the underlying user experience.

The payoff shows up downstream. A conversion rate problem caught in a prototype costs an afternoon. The same problem caught after launch costs a rebuild, a support queue and a quarter of lost revenue.

A prototype's whole job is to be wrong cheaply, before it gets built expensively.

How it shows up

Prototyping shows up as clickable Figma files passed around before a developer touches a line of code. It shows up in usability testing sessions where a facilitator watches someone try to complete a task using an unfinished design. It shows up in the gap between a stakeholder saying 'looks great' and a real user getting stuck on step two. When that gap is large, it usually means the prototype was shown to the wrong audience, or shown too late to change anything meaningful.

The Australian context

Australian teams working with distributed or outsourced development often lean harder on prototypes because the cost of miscommunication across time zones is higher. A clickable prototype removes ambiguity that a written brief can't, which matters when the person building the feature isn't in the same room to ask a quick question.

Where people get this wrong

Jumping straight to high-fidelity visuals.Polishing colours and type before testing the flow means any structural problem discovered later requires redoing finished work, not draft work.
Only testing the prototype internally.Internal teams already know how the product is supposed to work. Real usability testing needs people who've never seen it before.
Treating the prototype as the spec developers must copy exactly.A prototype communicates intent, not pixel-perfect production requirements. Treating it as gospel removes the flexibility developers need to solve real technical constraints.

Related terms

Common questions

What's the difference between a prototype and a wireframe?

A wireframe is a rough layout with boxes and labels showing structure only. A prototype adds interactivity, letting someone click through a flow as if it were real. Wireframes test layout, prototypes test behaviour.

Do I need a prototype before every project?

Not every project needs a high-fidelity prototype. Small, low-risk changes might only need a wireframe or a quick sketch. Anything involving a new user flow, checkout process or unfamiliar interaction pattern benefits from testing a prototype first.

What tools are used to build prototypes?

Figma is the most common tool for clickable prototypes, followed by tools like Adobe XD and Framer. For simpler flows, some teams still use paper sketches linked together, which is often enough to catch major usability problems.

How many people should test a prototype?

Usability research consistently finds that testing with around five users uncovers most of the major problems in a design. More users add diminishing returns for early-stage testing. Better to test early with five than wait to test with fifty.

Debrief

Get the next one

No spam. No fluff. Just the next article, straight to your inbox.

Keep exploring

About New Rebellion

New Rebellion is a marketing intelligence consultancy. We build tools, score Australian businesses on how their marketing actually performs, and publish Debrief every day. This dictionary is part of how we work in the open.

How we think →