Skip to content
Devlumio

Studio notes

Prototype the loop before you build the game

Art is the most expensive part of a game and the least useful early on. Here is the order we build in, and why the grey box comes first.

2 min readDevlumio
  • Games
  • Process

Every game pitch arrives with a mood board. Almost none arrive with an answer to the only question that matters: is the thing you do, over and over, actually fun?

That question is cheap to answer and expensive to postpone. So we answer it first.

The grey box comes first

Our first milestone on any game project is a playable build with no art. Boxes, flat colours, placeholder sounds. It looks like nothing. It answers everything:

  • 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 takes days to change. A polished level takes weeks. If the loop is wrong — and it usually is, the first time — you want to find out while changing it is still cheap.

What we watch during playtests

We do not ask people whether they liked it. People are kind, and kindness is not data. We watch for four things:

  1. Time to first understanding. How long before they stop asking what to do and start playing?
  2. Voluntary second run. Do they start another round without being prompted? That is the single strongest signal we have found.
  3. Where the hands go quiet. Idle hands mean the loop has a dead spot.
  4. 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.

We aim for something playable in the first six weeks, and we would rather show you an ugly build that works than a beautiful one that does not.

Keep reading

    • Process
    • Working together

    What a fixed-price estimate actually buys you

    Fixed price is not a discount and it is not a trap. It is a transfer of risk — and knowing which risk moved is the difference between a good contract and a bad one.

    2 min read

    • Mobile
    • Engineering

    React Native or native? A decision you can make in ten minutes

    The framework argument is mostly noise. Four questions decide it, and none of them are about which technology is better.

    2 min read

    • Working together
    • Engineering

    The handover is the product

    A launch that only one agency can maintain is not finished. What a real handover contains, and how to tell before you sign whether you will get one.

    2 min read

Have a project that needs this kind of thinking?

Send us a short brief. We reply within one business day.