Milestone map
Milestone map
3 milestones
Prototype a Core Game Loop with External Playtesters
6–10 weeks
Using Godot 4 (free, open source) or Unity (free personal tier), prototype a functional core game loop — the one essential mechanic the game is built around. The prototype does not need graphics or sound. Get at least five people outside your immediate network to play it and document specific feedback.
Proof required
Submit: a playable prototype (web build link or shareable file); a one-paragraph description of the core mechanic; and feedback notes from at least five external playtesters documenting what they found fun, confusing, or broken.
What gets checked
- The prototype demonstrates a specific core mechanic — not a collection of features without a unifying loop
- Playtester feedback is from at least five people outside the candidate's immediate network
- Feedback notes document specific observations — what they engaged with or struggled with
Common mistakes
- Building features before validating the core mechanic — a fully polished game with a broken loop fails
- Prototyping without external playtesters — developers cannot accurately perceive their own games as first-time players
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- Is the prototype playable without build environment setup?
- Does it demonstrate a specific core mechanic?
- Are playtester notes from at least five external people with specific observations?
Build the Complete Game with Polish
16–24 weeks (after milestone 1)
Build the full game around the validated core mechanic: complete levels or progression, sound effects, music, UI, and visual polish. Run a second round of external playtesting with at least five people and iterate based on their feedback.
Proof required
Submit: a playable build of the complete game; a list of features added beyond the prototype; and second-round feedback notes from at least five external playtesters documenting specific changes you made based on the first round.
What gets checked
- The complete game includes sound, UI, and visual polish beyond the prototype
- Second-round feedback is from at least five people with specific observations
- Feedback notes document specific changes made between the two rounds — the iteration is documented
Common mistakes
- Adding features without iterating on what the first playtest revealed about the core mechanic
- Skipping sound — first impressions from mobile players are heavily shaped by audio
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- Does the game have sound, UI, and visual polish?
- Are second-round playtester notes from five different people?
- Do the feedback notes document what changed between the two rounds?
Release on a Platform and Reach 100 Plays
2–6 weeks (release and promotion)
Release the game on a public platform accessible to mobile players — itch.io with mobile browser support or the Google Play Store. Document at least 100 plays or downloads and collect at least five external reviews. Write a 200-word retrospective on the development process.
Proof required
Submit: a public link to the released game; a dashboard screenshot showing at least 100 plays or downloads; at least five external reviews or feedback comments; and a 200-word retrospective covering what you would do differently on the next game.
What gets checked
- Game is publicly accessible to strangers — no invitation required
- At least 100 plays or downloads on the platform dashboard
- Retrospective identifies specific process lessons — not 'it took longer than expected'
Common mistakes
- Releasing in unlisted mode with no promotion — 100 plays requires active sharing
- Retrospective that lists missing features rather than process lessons
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- Is the game publicly accessible to strangers?
- Does the dashboard show at least 100 plays or downloads?
- Read the retrospective: does it name specific process lessons?
Part of