One testable question
Agree the user task, success signal and conditions that would reject the approach.
Realtime / Rapid Prototyping
Build the smallest prototype that answers the risky question.
Test a mechanic, interaction or technical assumption before committing to a larger build. The deliverable includes the decision the prototype supports.
Example starting scope
Can the user aim and act through gaze alone?
Gameplay prototypes
Implement only the input, feedback and loop needed to test the question.
A usable handoff
Deliver the prototype, source and a short record of observations and remaining risks.
Relevant work
Duck Hunt VR · gaze-based prototype
Bartosz’s published Google VR prototype combines aiming, movement and shooting through head movement, with Unity implementation, art and gameplay logic.
Project details
See the interaction example
What we check
Agree the result before implementation.
Decision before polish
Review the interaction against the agreed question before expanding art or features.
Known limits
Record what was tested and what still needs production implementation.
Related scopes and guides
Choose the next step.
Rapid prototyping questions.
Does a prototype need final art?
Usually not. Visual polish should be added only when it materially improves the decision, test or presentation purpose.
Can the prototype become production code?
Sometimes, but that should not be assumed. The first goal is a trustworthy proof; useful parts can then be productionized deliberately.
Your project
Have an idea that needs proof before larger production?
Send the risky assumption, target platform and what decision the prototype needs to support.