The Finish Line Is Shade: Three Solo Devs on Shipping Small Without Getting Cooked

A six-hour game is not a failure. It is a sentence that knows where the period goes. That should be an obvious thing to say in 2026, but the indie conversation still has a bad habit of treating small games like appetizers that forgot to become meals. A tight six-hour release gets called short. A solo developer who ships one gets asked when the real version is coming. Meanwhile, the real version is often a burned-out person staring at a feature list they never needed.

I talked with three solo developers this fall about shipping small without cooking themselves. All three have 2026 releases in the six-to-eight-hour range. All three have opinions about scope, and none of them romanticize the grind. The conversations have been edited for length and clarity, which is also what good scope control looks like.

The Scope Is the Sunscreen

Every solo dev I spoke with described scope as a form of protection. Not protection from ambition, exactly. Protection from the specific kind of ambition that turns a two-person idea into a five-year debt. The useful question is not how big can this game be. It is how much game can I finish without hating the sight of it.

That sounds unglamorous. Good. Glamour is what gets people to build a crafting system because a forum post asked for one.

Mara Voss, Tin Can Sun: Cut the Menu, Keep the Porch

Mara Voss shipped her first solo game, a six-hour repair drama about a desert bus depot, after two years of part-time work. She describes her early build as a cautionary tale in feature creep.

'I had a faction reputation system and no factions,' Voss said. 'I had a weather sim that mostly made the screen gray. The game got better when I admitted the porch was the game. People came for the porch. They did not come for a spreadsheet about radiator parts.'

Voss cut three systems in one week and replaced them with one idea: every repair should change how the depot sounds. A fixed pump hums. A broken one clicks. By the end, the bus depot feels like an instrument you are slowly tuning. That is a small feature with a large effect, which is the whole trick.

Her advice for solo devs is blunt. 'If a feature cannot survive being explained in one sentence at a bus stop, it is probably a second game. Put it in a notebook and finish the first one.'

Devon Pike, Lost Sock Studio: A Six-Hour Game Is a Finished Sentence

Devon Pike makes small tactical games out of a spare room in Maine. His 2026 release is a six-hour campaign with no procedural mode, no live-service roadmap, and no plans to become a lifestyle.

'I keep seeing short used as a criticism,' Pike said. 'But a six-hour game can be complete. A twelve-hour game can be padded. Nobody says a album is bad because it is forty minutes. They say it is bad because the last three songs are filler. Same thing.'

Pike spends most of his development time on the first thirty minutes of play. He calls it the porch test: if a new player cannot understand the fantasy before the sun moves across the porch, the game is not ready. That focus keeps his projects small and his weekends intact.

'Burnout is not a badge,' he said. 'It is a scope problem with a human face. I have shipped small games that I am proud of. I have also shipped nothing for a year because I was trying to make a big game out of spite. The first one pays better, emotionally.'

June Okafor, Porch Cat Games: Finish Before the Heat Breaks You

June Okafor's 2026 release is a seven-hour mystery set in a failing movie theater. She works a day job and builds games in the early morning, which means her scope decisions are not theoretical. They are survival.

'I used to think finishing small meant I was not serious,' Okafor said. 'Then I realized seriousness is finishing. A six-hour game that exists beats a forty-hour game that lives in my head and makes me feel guilty at dinner.'

Her method is almost boring, which is why it works. She writes the ending first. Then she builds only the systems the ending needs. If a feature does not help the player reach that ending, it goes on a list called Later, which is really a list called Probably Never. She also schedules one full week of doing nothing after a launch. Not a vacation. A cooldown.

'You cannot ship a game about shade if you are standing in the sun the whole time,' she said. 'That is not a metaphor. I mean it. Take the walk. Eat the meal. The game will still be there.'

What Finishing Actually Looks Like

All three developers described the end of a project as less of a victory lap and more of a quiet exhale. The game gets small. The list gets shorter. The last month is not about adding features. It is about removing the ones that no longer earn their place.

That is the part the indie scene does not post about. We post the trailer. We post the launch. We do not post the moment a solo dev closes a document called maybe_multiplayer and feels their shoulders drop two inches.

Small games are not a compromise. They are a choice about where to spend a life. A six-hour game can be a complete thought, a clean finish, and a developer who still wants to make another one. That sounds like success to me.

The Shade Is the Point

Sunburned Games is not here to tell you every game should be short. Some games earn their length. But length is not a virtue by itself, and scope is not a personality. The solo devs who last are the ones who learn to build shade for themselves: smaller plans, honest deadlines, and a finish line they can actually reach before the heat breaks them.

A game does not need to be huge to matter. It needs to be finished. And the person who finishes it needs to still be standing.