Should You Quit Your Job to Make Games?

“Should You Quit Your Job to Make Games?” is a question almost everyone asks before or during their first game, and it deserves an honest answer rather than a motivational one. The honest version: Usually not at first — most successful indie developers start part-time and only go full-time once there is real evidence it can work. This guide gives you the practical picture, not the hype.

The honest answer

Usually not at first — most successful indie developers start part-time and only go full-time once there is real evidence it can work. The thing worth internalising is that quitting early dramatically raises the financial pressure and risk, which rarely helps the work. That reframes the question from a search for a magic number or shortcut into something you can actually plan around.

It is easy to find both wildly optimistic and doom-laden takes on this online. The truth is usually in between and, more importantly, depends heavily on your specific choices — which is good news, because it means a lot of it is in your control.

Let real players be the judge

It's remarkable how differently real players behave from how you imagine they will. The tutorial you think is obvious confuses them; the feature you agonised over goes unnoticed; the thing you almost cut becomes their favourite. None of that is visible from inside your own head, which is why watching real people play is the single highest-leverage thing most developers under-do.

Watch without intervening, resist the urge to explain, and pay attention to what players do as much as what they say. Their confusion and their choices are data, and acting on that data is what turns a game that works for you into one that works for everyone.

Plan for the parts you can't see

Once a game leaves your machine, a lot of what happens to it becomes invisible by default. Players run it on hardware you don't own, hit problems you never reproduced, and most of them never tell you — they simply move on. The gap between 'it works for me' and 'it works for everyone' is where a surprising amount of churn quietly lives.

So plan to see what you otherwise couldn't. Watching real players, capturing the bugs and crashes they hit with the context to fix them, and paying attention to where they drop off all turn invisible problems into ones you can actually act on — which protects the reviews and retention everything else depends on.

Start before you feel ready

Almost everything in indie development rewards starting earlier than feels comfortable — the store page, the audience, the playtesting, the marketing. The instinct is to wait until things are polished before showing anyone, but that instinct costs you the runway you need most. The audience you build over months is what makes a launch work; it can't be conjured in the final week.

So bias toward starting now, even roughly. Put the thing out, tell people about it, get it in front of players. You can refine as you go, and the feedback you get early is far more valuable than the polish you'd have added in private.

Consistency beats intensity

Indie development is a long game, and it rewards steady, sustainable effort more than heroic bursts. A little progress made consistently — on the game, on the marketing, on the community — compounds in a way that last-minute sprints never do. The developers who finish and find an audience are usually the ones who kept showing up, not the ones who worked themselves into the ground for a week and then burned out.

Build a pace you can sustain, and protect it. Momentum is fragile and expensive to rebuild, so steady forward motion is worth more than any single intense push.

Polish where players actually look

Polish is not evenly valuable. Players form an impression in the first minutes and spend most of their time in the core loop, so effort spent there returns far more than effort spread thin across content few people reach. The opening, the moment-to-moment feel, and the things every player touches are where polish converts directly into how good the game feels.

Be deliberate about it. Make the first impression strong and the core interactions satisfying before widening out, because a great core with less content almost always beats a sprawling game that never feels good to play.

What to do about it

Practically: start part-time, prove the project and the audience, and only go full-time with runway and evidence, not hope. That advice is boring on purpose, because the boring fundamentals are what actually work. The developers who do well here are rarely the ones with the cleverest shortcut; they are the ones who made sensible choices and stuck with them.

Whatever the specifics, start smaller than feels exciting, get something real in front of players, and let what you learn shape the next step. That single habit answers a surprising number of these questions in practice.

The best feedback comes from watching someone play without you talking. Get there as early as you can.