A game pitch can communicate a strong visual direction without answering a crucial question: is the thing you do, over and over, actually fun?
An early prototype can help answer that question before a larger investment in art and content.
The grey box comes first
A useful first milestone can be a playable build with simple boxes, flat colours, and placeholder sounds. Its scope and timing depend on the core interaction, platform, and technical questions. It can help explore:
- Does the core action feel good on the tenth repetition?
- Is the difficulty curve doing anything, or is it just noise?
- Can a stranger understand the goal without being told?
A grey box usually gives you less work to revise than a polished level. If the loop needs to change, it helps to find that out before detailed art and content depend on it.
What to watch during playtests
Ask what people thought, and compare their answers with what they actually did. A playtest can look for four useful signals:
- Time to first understanding. How long before they stop asking what to do and start playing?
- Voluntary second run. Do they start another round without being prompted? That is a useful signal of interest to investigate alongside the other observations.
- Where the hands go quiet. Idle hands mean the loop has a dead spot.
- What they say afterwards, unprompted. If they describe a mechanic you did not design, that mechanic is what your game is actually about.
Then, and only then, the art
Once the loop holds attention, art stops being a gamble and becomes an amplifier. You know what the player looks at, so you know where the detail belongs. You know the pacing, so you know where music should swell. Every hour of art goes somewhere useful instead of decorating a mechanic that gets cut in month four.
This ordering is not unique to games. It is the same argument for wireframes before visual design, and for an API before a dashboard: do the cheap experiment that can kill the idea, before the expensive work that assumes it survived.
What this means if you are hiring a studio
Ask any studio you are talking to when you will first be able to play something. If the answer is a number of months, ask why. There are legitimate reasons — a heavy simulation, a bespoke engine — but "we design the whole game first" is not one of them.
Agree on the smallest useful playable milestone and what it needs to demonstrate. At Devlumio, the prototype scope, target devices, playtest coverage, and schedule belong in the project proposal. A rough build can make the next decision clearer without committing to a full game release.