Prototypes
Use interactive HTML prototypes to try product flows, behavior, and states.
A prototype lets you try part of an app before building or changing the real product. An agent can make a self-contained HTML prototype with realistic content and enough behavior to show how the flow works.
Exercise the states that could reverse the decision.
- Path
- Resolve one blocker and prepare a release.
- States
- Blocked, pending, failure, recovery, and ready are operable.
- Boundary
- The prototype demonstrates behavior without claiming a backend.
What a prototype can show
- a multi-step flow;
- loading, empty, error, and success states;
- validation and feedback;
- keyboard and mobile behavior;
- transitions between views or modes.
It does not need to be the whole product
A useful prototype can cover one important path and the states around it. It does not need a backend, every screen, or every edge case. It should be clear which parts work and which parts are only visual.
DiagramsSee how HTML can explain architecture, sequence, state, and flow.