Solo dev postmortem: Freerunners

A solo developer spent years building a parkour game in evenings and weekends, shipped it on March 4, 2026, and then wrote that one of his biggest mistakes was thinking the hard part would be the idea instead of the sheer volume of work. James Rowbotham’s postmortem says Freerunners “took a long time,” sold poorly, and still taught him more than a smoother project would have. (moddb.com, store.steampowered.com) Freerunners is not a tiny prototype dressed up as a full game. Its Steam page lists 50 handcrafted levels, a full movement set built around vaulting, climbing, swinging, sliding, and flipping, and a launch price of $11.99. (store.steampowered.com) That scale is the whole story. Rowbotham says he originally planned 100 levels, then cut the number to 50 after his wife asked if 100 was really a good idea, and he now says that one cut probably saved the project. (moddb.com) He also says the genre choice hurt him in ways that only showed up later. A precision platformer about movement “flow” needs lots of bespoke level design, careful tuning, and repeated testing, which means every new stage is less like copying a room in a building and more like hand-cutting another key. (moddb.com, store.steampowered.com) By February 2024, he already had all 50 levels playable with art and was using Steam Next Fest as a milestone to gather feedback and wishlists. Even then, the game was still not ready to launch, which is the kind of schedule slip that happens when “mostly there” still hides months of polish, bug fixing, and redesign. (gamedeveloper.com, cbgamedev.com) The demo taught the same lesson in miniature. Rowbotham first tried to build a showcase slice from the middle of the game, then scrapped that plan because new players needed the early levels to learn the controls, so even the demo had to be rebuilt around onboarding instead of spectacle. (gamedeveloper.com, cbgamedev.com) His blunt summary is that solo developers are the bottleneck for everything. Art, code, level design, feedback, bug fixing, store setup, and marketing all queue behind one person, so a bad estimate does not miss by 10 percent the way a short grocery list does; it can miss by years the way a house renovation does. (moddb.com) He says lack of hard deadlines made the project drift, and constant replanning was often a sign that the game needed less scope, not a smarter calendar. That is a useful correction to the usual solo-dev fantasy, where discipline is treated like the answer to everything even when the real problem is that one person picked a job sized for three. (moddb.com) The postmortem is not a doom story so much as a cost ledger. Rowbotham says the game was not a financial success, but he did not depend on it to survive, and he came away as a better developer with a finished commercial release on Steam. (moddb.com, store.steampowered.com) The part worth remembering is simple: underestimating scope does not just make a project late. It locks you into old tech, old decisions, and years you cannot spend on the next idea, which is why Rowbotham’s clearest advice is to cut earlier, get feedback sooner, and ask whether doing it all alone is actually the point. (moddb.com)