72h to a playable prototype
The format, the constraints, a concrete example, and why time pressure creates direction.
The starting constraint
In 72 hours, there is no time to get the scope wrong. You have to scope, code and deliver a playable build. Not a document. Not a mockup.
The format works precisely because it forces brutal reduction. There is no room for five average mechanics.
Who this format is for
An indie dev who wants to test a mechanic before investing weeks. A studio that needs a prototype to pitch. A team that wants to enter a game jam with a solid base.
The goal is not to finish a game in three days. The goal is to move past intention.
What the three days look like
- Day 1: scoping, minimal architecture, first playable loop.
- Day 2: systems integration, game feel, first complete tests.
- Day 3: adjustments, blocking fixes, short documentation, build delivery.
A concrete example
Minigame Factory was an ideal playground for this format. Color Flood, Stack Tower, Orbit Tap and Lock Pick were produced with the same logic: tight scope, playable build, standardized API.
Some prototypes turned out promising, others showed their limits quickly. That is a success, not a failure: the format is meant to learn fast.
What the format does not do
No HD assets, no custom audio, no backend, no final polish. A functional prototype is not a finished product.
This format replaces weeks of doubt with three days of verification. That is its real value.