Every solo dev I know has hit the same wall. The first few weeks of a project are electric. You can see the whole thing in your head, the ideas won't stop coming, and you'd happily skip meals to keep building. Then, somewhere around week six or month three, the electricity goes out. The work is still there. The excitement isn't.
This isn't a character flaw and it isn't a sign you picked the wrong project. It's the shape of every long piece of solo work. You will not feel motivated all the time, because nobody does. What you can do is build something that keeps you moving when the motivation is gone.
The short version
If you only take a few things away, take these. The rest of the post unpacks each one.
- Stop waiting to feel motivated. Build habits that still produce something on a flat day.
- Shrink the next task until it's almost embarrassingly small, then start there.
- Set a daily minimum you can hit even on your worst day, and protect the streak.
- Keep a visible record of what you've finished, on screen or on paper.
- Beat isolation on purpose: find other devs, post devlogs, get one person to hold you to it.
- Compare yourself to last month's you, never to someone else's finished game.
- Treat rest, food, exercise and people as part of the schedule, not a reward you earn.
Motivation is a bad thing to depend on
Motivation is a feeling, and feelings come and go for reasons you don't control. You slept badly. The bug you spent all day on wasn't the real bug. Someone posted a screenshot of their game that made yours look like a student project. Any of those can flatten your drive for a day, and if your ability to work depends on feeling driven, you've just lost a day.
The developers who finish things have arranged their work so that a flat day still produces something. They've quietly stopped asking "do I feel like working" and started asking "what's the next small thing I said I'd do".
Shrink the task until it's stupidly small
When you can't face the work, the task in your head is almost always too big. "Build the inventory system" is not a task, it's a project, and staring at it does nothing but make you tired.
The fix is to shrink the next step until it's almost embarrassingly small. Not "build the inventory system" but "add one slot to the inventory grid". Not "do the audio pass" but "wire up the sound for the door opening". A task you can picture finishing in twenty minutes is a task you can start, and starting is the whole problem. Momentum almost always shows up once you're moving, it just refuses to show up beforehand.
On genuinely bad days, shrink it further. Open the project. Read the code you wrote yesterday. That's allowed to be the whole session. More often than not, once the file is open you'll fix one small thing, and one small thing is infinitely more than zero.
Set a daily minimum you can hit on your worst day
Pick a floor. Something so small that you'd feel silly not doing it even when you're exhausted or fed up. Fifteen minutes. One commit. One asset placed. One line of design doc.
The output barely matters. What the minimum protects is the streak. A chain of tiny days keeps the project alive in your head and stops the restart cost from piling up. If you skip a project for a fortnight, coming back costs you an afternoon just remembering where you were. If you touched it yesterday, you're already warm.
Some days you'll hit the minimum and stop, and that's fine. Plenty of days you'll hit the minimum and then keep going for two hours because you were never really tired, you were just staring at something too big. The minimum only has to get you to the desk. Most of the time, once you're there, you keep going.
Make progress visible, because your brain won't do it for you
The cruel thing about the middle of a project is that progress stops feeling like progress. The exciting, visible milestones are behind you and ahead of you, and the middle is a thousand small tasks that don't individually look like much. Left alone, your brain will happily conclude you've done nothing for a month.
So don't leave it alone. Keep a record it can't argue with. A "done" list you actually add to, a devlog you post every week whether or not anyone reads it, a folder of dated screenshots you can scroll back through. When the doubt shows up, you want evidence sitting right there. The version of your game from three months ago is the proof, and if you never captured it, the doubt wins by default.
None of this has to happen in front of a computer either. Grab a notebook and sketch the inventory system you've been putting off. Scribble down a world-building idea before it evaporates. Draw the level on graph paper. A page of notes from a walk is still a record of a day you moved the project forward, and some days it's the easiest kind to make.
This is one place a bit of tooling earns its keep. Being able to scroll back through what you've built, the sprites you've drawn, the models you've made, the packs you've assembled, is a quiet antidote to the feeling that you're standing still. Half the time you're much further along than it feels. (It's a big part of why I organise my asset library so I can actually see it.)
Isolation is the real enemy, not the work
The work is rarely what breaks people. Working entirely alone for months is what breaks people. No colleague to tell you the idea's good. Nobody to notice you shipped the thing. No standup where you say out loud what you did yesterday and quietly realise it was quite a lot.
You have to manufacture what a team gives you for free. Find a Discord of other solo devs (the AssetHoard Discord is one) and actually turn up in it. Post your devlog even to an audience of nine. Tell one friend what you're shipping this week so there's a human who'll ask how it went. Pair up with another dev and trade weekly check-ins. None of this is marketing. It keeps the work real to someone other than you. Externalising your progress to even one other person changes how the work feels, because suddenly you're not the only one who knows it exists.
If in-person is an option, take it. A monthly indie meetup or a game jam can reset your whole outlook in an afternoon, mostly by reminding you that everyone else is also stuck on something and doubting themselves too.
Stop comparing your middle to someone else's end
The screenshot that ruined your afternoon was a finished, polished, cherry-picked frame of someone else's months of unglamorous work. You compared it to your actual Tuesday, bugs and placeholder art and all. Of course you lost.
Everything you see online is a highlight. The trailer, the launch post, the "we hit a thousand wishlists" thread. You don't see the fortnight they spent fighting the same engine bug you're fighting, or the three redesigns they binned, or the week they didn't open the project at all. Comparison isn't just unkind to yourself, it's inaccurate, because you're missing most of the data.
The only honest comparison is you against you. Are you further along than last month? Then it's working.
Protect your life, not just your rest
A lot of solo devs treat rest as a reward they have to unlock by working hard enough, which means they never quite unlock it, which means they run flat out until they crash. Then they lose two weeks to burnout and call themselves lazy for it.
Rest isn't earned, it's part of the schedule. So is eating well, exercising, and spending time with friends and family. None of that is what you do once the real work is finished, it's the space that lets you recharge between sessions of the real work. Build it in on purpose. Take one full day off a week and don't touch the project. Stop at a set time most evenings. Go outside. The ideas that untangle your worst problems almost never arrive while you're grinding at the desk, they turn up in the shower, on a walk, doing the washing up. A rested brain is a faster brain, and a burned-out one ships nothing at all.
Burnout is not a badge. It's a project risk, and it's your job to manage it like any other.
What it actually takes
Staying motivated as a solo dev is mostly a matter of not needing to be motivated. You build small habits, you make your progress visible, you find a few humans to be accountable to, you rest before you're wrecked, and you keep comparing yourself only to yesterday's version of yourself.
Do that, and the flat days stop being a threat. They become just another Tuesday where you hit your minimum, close the laptop, and come back tomorrow. The people who finish games aren't superhuman. They just kept turning up through the boring middle, one small task at a time, until the finish line quietly showed up.
Keep turning up.
The AssetHoard Team
Hero photo by JC Gellidon on Unsplash.
Frequently asked questions
Solo indie developers usually lose motivation because of how long solo work is structured, not because they're lazy. The common causes are the long middle of a project where progress stops feeling visible, working in isolation with nobody to bounce off, comparing your day-one work to someone else's finished game, and burning out from treating rest as a reward you have to earn rather than part of the schedule. Motivation dips are a normal part of any long project, not a sign you've chosen the wrong one.
Stop relying on motivation and lean on habit instead. Set a small, non-negotiable daily minimum you can hit even on a bad day, shrink your tasks until the next step is obvious, and keep a visible record of what you've finished so progress stops being invisible. Motivation gets you started; systems keep you going once the novelty wears off.
Yes. The middle of a project is where the excitement of starting has faded and the reward of finishing is still far away, so almost everyone wants to quit there at least once. Wanting to quit is not the same as needing to. The developers who ship are rarely the most motivated ones. They're the ones who kept a steady pace through the part where it stopped being fun.
Treat burnout as a project risk and schedule against it. Build rest, sleep, exercise and time with people into your week instead of saving them as a reward for hard work, take at least one full day off the project each week, and stop at a set time most evenings. Burnout usually comes from long stretches of running flat out with no team to notice you're struggling, so watch for the early signs, like dreading opening the project or losing interest in ideas you used to love, and ease off before you crash rather than after.
There's no single right number. Consistency matters far more than daily hours. A small daily minimum you can hit every day, even fifteen minutes or one commit, keeps a project moving better than occasional twelve-hour sprints followed by a week off. Pick a pace you could keep up for a year, set a stopping time, and let good days run longer on their own. If you're working around a day job, a few focused hours a week done steadily will still finish a game that's scoped to fit.
The ones that remove friction, so the hours you do have go into the game rather than fighting your setup. A code editor you know inside out, a Git client that makes committing and rolling back painless, and an asset manager such as AssetHoard so you can find and preview the sprites, models and sounds you already own instead of digging through folders or buying them twice. Add a simple task list for keeping the next step small, and a playlist of banging tunes to get you into the zone. None of these make you motivated, but every bit of friction you remove makes it easier to start on a flat day.