The quick read
- Include a default state, an empty state and a result after user input.
- Ask someone to complete the task without explaining the interface first.
Choose the interaction
Identify the moment you want to test: filtering a collection, stepping through onboarding or comparing options. Provide the content and visual constraints that matter. A narrow interaction makes feedback easier to interpret than a complete app full of assumptions.
Use realistic states
Include a default state, an empty state and a result after user input. For an illustrative booking concept, show what happens when a preferred time is unavailable. Preserve the relationship between design intent and the actual behaviour of the prototype.
Observe users
Ask someone to complete the task without explaining the interface first. Watch where they hesitate and whether labels match their expectations. Check keyboard access and small-screen layout. Verify current product capabilities and export options before assuming the prototype fits a production workflow. The value of an interactive design concept lies in the questions it helps answer. It should reveal whether the proposed experience is understandable, not merely demonstrate that screens can be connected.
Sources & notes
Source-based guide, not a hands-on product test. Features and availability can change.
figma.com — official reference
Sources reviewed for the September 2026 launch edition.