What it is
Prototypes built in actual code (HTML/CSS/JS or a framework) that behave like the real product, used to test complex interactions, real data, performance, or technical feasibility that design tools cannot simulate.
When to use it
During Prototype, for interactions, data behavior, or feasibility questions that clickable prototypes cannot answer.
Why (value)
Provides the most realistic testable artifact short of production, and validates technical feasibility alongside experience.
How to run it
- Decide what specifically needs real-code fidelity.
- Build a focused front-end prototype.
- Use realistic data and interactions.
- Test with users and/or assess feasibility.
- Feed learnings into design and engineering.
Inputs and outputs
- Inputs: Front-end skills or tools, design specs, sometimes real data.
- Outputs: A working prototype validating interaction and feasibility.
Time and effort
High. Real development effort.
Evidence and limitations
Highly realistic, but still a proxy unless tested with real users on real tasks; feasibility findings are strong, experience findings still need user validation. See Evidence and limitations.
Tips and pitfalls
- Scope tightly, do not build the whole product.
- Use for what design tools cannot fake.
- Keep it disposable unless you plan to evolve it.
Variations
Throwaway prototypes, evolutionary prototypes, AI-generated code prototypes.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Interactive prototyping — Build a clickable simulation of the experience so people can try it before it is built.
- AI prototyping — Use AI tools to generate working prototypes from prompts in minutes, not days.
- Design pairing — Two people design together in real time, combining perspectives and catching issues early.
