- The first line says this is a concept and names what it does not model.
- Each screen answers one review question, and that question is written on the page.
- Sample values are marked as samples and do not look like real records.
- No price, date, availability or promise appears unless the team has confirmed it.
- Placeholder controls, such as a confirm button, are described as placeholders.
- The page shows the date of this draft and the version it replaces, if there is one.
- Reviewers are told where to send reactions, and by when.
- Names, addresses and account details are invented, not copied from real customers.
Technical & ProductContent Creator
Interactive prototype: a concept page reviewers can react to, not a working product
An interactive prototype, in this sense, is a concept page that looks clickable, so a reviewer can react to layout and wording before anything is built. It works best for one question at a time, such as whether the first screen makes sense or whether a label is clear. It does not model logic, data or full user flows, so use a dedicated prototyping tool when the answer depends on those.
What people search
Interactive prototype: 260 average monthly searches.Google Ads Keyword Planner · 2026-10-09 · United States
Weak and strong wording
Turn a general invitation into a question reviewers can answer
Weak: Click around and tell us what you think.
Strong: Look at the first screen only. What is the one thing you would change before choosing a stop?
A specific question about one screen gets a usable answer. A general invitation gets opinions about everything, often about colors.
Weak: This is the final app.
Strong: This is a concept for review. Screens, wording and order may all change.
The label stops reviewers and future customers from treating a mockup as a commitment, a live feature or a finished price.
Weak: Everything works great.
Strong: Tell us which label on this screen a first-time rider might misread, and why.
Asks for a judgment the page can test. Praise for an unfinished concept tells you very little about the design.
Weak: Let us know any feedback.
Strong: Reply by Friday with your answers to the three questions in the last section.
A deadline and a fixed set of questions keep the round small enough to finish and make the answers easy to compare.
Example excerpt
Sample concept page: booking a campus shuttle seat
Sample section
Illustrative example: the shuttle service, its stops and its times are fictional. Concept: campus shuttle booking, first draft This page shows two screens. It is a layout for review, not a working booking tool. Nothing is reserved, and the times are placeholders. Screen 1: Choose a stop Riders pick a pickup stop from a list of six, then choose a time window. The screen shows the next three departures for the chosen stop, using sample times. Screen 2: Confirm your seat The rider sees the stop, the time window, the number of seats and a short note about cancellation. The confirm button is a placeholder for layout review. Questions for this round 1. On Screen 1, is it clear which stop you are choosing? 2. On Screen 2, would a first-time rider know what happens after they confirm? 3. Is the cancellation note in a place you would read before confirming? Not part of this review: pricing, accessibility testing and rules for full vehicles. Those are tested with a working version.
Section outline
Sections of a concept page for review
Concept statement
One or two sentences on what the idea is and who it is for, labeled as a concept on the first line.
60 wordsScreens in order
Each screen as a short block with its purpose and the main content it shows. Keep to the three to five screens that matter for the question.
220 wordsReview questions
Two to four questions tied to specific screens, asking about clarity, order or wording.
100 wordsOut of scope
What this round will not test, such as logic, data, pricing, security and performance.
60 wordsWhat happens next
How the reactions will be collected, the date they are due, and the decision they will inform.
60 words
Total: 500 words
Quality checklist
Check that the concept cannot be mistaken for the product
Mistakes to avoid
Ways a concept page gets misread
Presenting a concept as the product
A page that looks finished gets quoted back to you. Label the concept on the first screen and in any sharing message, and state what has not been decided.
Asking for a verdict on everything
Reviewers who get fifteen questions often answer only a few of them well. Choose two to four questions that would change a decision this week.
Using real customer data in samples
Names, addresses and account numbers from real customers do not belong in a concept page, even as examples. Invent values that cannot be mistaken for real records.
Hiding the scope
If reviewers do not know that logic, pricing and testing are missing, they will assume those are planned. Put the out-of-scope list before the first screen.
Asking a concept page to answer a task question
A concept page cannot show whether people complete a real task, because nothing on it runs the task. Use a tool built for flows and testing when that is the question.
Share the finished page
Share the concept with the people who will decide
Team link
The usual choice for internal review. Only workspace members can open a team link, so share it with the people who will decide, provided they are members, and name the date by which you want reactions.
Public link
Use a public link only for a concept you are ready to show outside the team, such as an early group of users. Remove internal notes before you share it that way.
WhatsApp share button
The WhatsApp share button sends the public link, so use it only for a concept you are ready to publish. Send a short message with the review question and the link. Ask for a reaction to one screen rather than to the whole concept.
HTML download
Download the HTML file to keep the exact version you showed. Put the review date in the file name so later changes do not blur the feedback you received.
Frequently asked questions
Can a concept page replace a full prototyping tool?
Not when the question depends on flows, component states or how a screen reacts to input. A concept page shows layout and wording for review. For clickable flows and handoff to developers, use a prototyping tool built for that work.
How many screens should an interactive prototype have?
Include only the screens the review question needs. Each extra screen gives reviewers another place to get lost, and a screen that answers no question should be left out.
Is an interactive prototype template enough to start?
A template can give you the layout, but the screens, labels and sample values must come from your concept. Keep the wording that marks the page as a concept, and replace any sample content a reviewer might mistake for real.
Can I show app interface designs on this page?
You can describe a screen in text and sample values, or add an image of a screen if the image is labeled as a draft. An image does not behave like the interface, so say so on the page and keep the review questions focused on what a reader can see.
Browse by category
More pages in Technical & Product
Pages
Status Page
Documents
Technical Specification
Reports
Wait-time Dashboard
References
Tutorial Page
References
Code Snippet Library
References
API Documentation
How to build it
Follow the eight-step wizard: type, assets and description, images, branding, contact and call to action, Atty Suggestions, blueprint, and generate. Atty generates one HTML page in the background. Review it, then publish and share the page link or download the HTML file.
