Code
Build a clickable prototype
A real interactive mock you can hand someone to try.
Fill it in
The screens and what happens between them.
Which frame.
Things you tick stay ticked between screens.
Your prompt
Build a clickable prototype for Phone. [the app] Make it FEEL real. The point of a prototype is to find out whether the flow works by watching someone use it, and that only happens if tapping things responds the way they expect. Dead buttons end the test, because the person starts asking what is real instead of using it. Keep state across screens: things ticked stay ticked, added items appear in the list. Without that, the second screen contradicts the first and the illusion goes. Use realistic content, not lorem ipsum and not perfect data. Long names, empty states and a list of one are where designs break. One self-contained HTML file.
Use Build a clickable prototypeOpens with everything above already filled in.
Why this works
Dead buttons end a usability test, because the person starts asking what is real instead of using it. This keeps state across screens and uses realistic content rather than lorem ipsum, since long names, empty states and a list of one are where designs actually break.