Repository navigation
Research Open Development Plan
A scaffolding document. The essay earns its argument through peer evidence before it ever names itself.
Single claim to land: For a new indie developer with no audience, no budget, and no break, working in the open is not a sacrifice of advantage but the substantive source of it. The mark a new indie needs to make is made by people who watched it being made.
The build. Each sub-claim is earned by the one before:
- The hardest thing for a new indie to do is make a mark. (Establish the problem as felt, not abstract.)
- A mark is not a launch. A mark is recognition by people who already know who you are. (Reframe what success looks like.)
- Recognition before launch only happens when the work is visible before launch. (Name the mechanism.)
- The games that carried their makers furthest were, with startling consistency, the ones made where people could see them. (Weight of evidence: peer games.)
- The same pattern holds outside games. Open work has built operating systems, creative tools, and careers. (Lineage: FOSS, build-in-public.)
- The apparent costs of openness (theft, loss of mystique, exposure of failure) turn into the very things that build trust. (Answer the objections.)
- Openness is not a strategy the struggling indie adopts. It is the condition under which the struggling indie is found. (Land the thesis.)
- The mark is made by a community that recognises itself in the work. (Close on the image.)
The felt problem. Steam ships hundreds of games a week. A new developer with no audience is competing for existence. The phrase "the hardest thing for a new indie to do is make a mark" lands here and becomes the throughline. Closes on a specific image: a page on Steam with twelve views, the maker refreshing it at midnight.
Reframe. A mark is not a Steam launch. It is the moment a stranger starts telling other strangers about you before you have asked them to. Marketing manufactures this after the fact; open development grows it from the start. Closes: marks are made by people, not algorithms.
Team Cherry's Hollow Knight campaign. AU$57k closed with ~2,100 backers. The mark was made before the money arrived. Closes: the 2,100 people were the achievement, not the dollar figure.
ConcernedApe's four-and-a-half years on Chucklefish. Bay 12 Games on Dwarf Fortress for twenty years. Freehold on Caves of Qud. The audience gives feedback the lone developer cannot otherwise have and becomes the audience. Closes: the devlog is not content; it is the work, shown.
Wube's Friday Facts (over a decade weekly). Maddy Thorson open-sourcing Celeste. Transparency as engineering culture that the marketing trails. Closes: what a player trusts is a maker who has been trustworthy in public for long enough to prove it.
Anuke's Mindustry under GPLv3 on Steam. tobspr's Shapez. Godot and Blender underneath a generation of indie work. The commercial product was never really the binary; it was the relationship with the people making it better. Closes on an image of a commit from a stranger landing, the game getting better, the commons growing.
Linux. Buffer's open salaries. Pieter Levels' public revenue. Build-in-public as a noticed pattern, not an invention. Benkler's Wealth of Networks and Shirky's Cognitive Surplus on gift economies outproducing closed ones for creative work. Closes: games arrived at this late; they are arriving now.
Named honestly, answered concretely. Theft, indifference, exposed failure, unpaid openness, solo-dev risk. Closes: the fears are not wrong. They are smaller than the thing on the other side of them.
The close. Marks are made by the community gathered around the work. Contributor in the credits. First pull request. Three-year backer. This is where Volley! can appear once, as the proving grounds for a new way to make games. Closes on the chosen closing image.
A. The Adams brothers at a desk. Twenty-plus years of public Dwarf Fortress notes. A single kitchen, a single screen, one reply to a bug report at one in the morning. The longest-running public development project in commercial games.
B. The Friday Facts that almost did not ship. Wube's first Friday Facts post, 2013. A tiny game called Factorio with almost no audience. The team committed to writing every Friday. Ten years later the blog has more readers than most indie games will ever see.
C. The Kickstarter page at AU$57,000. Team Cherry's Hollow Knight campaign closes in late 2014. 2,158 backers, AU$57,138. Three people in Adelaide. The 2,158 were the mark.
Recommendation: Option C for directness; Option A for longer emotional runway. Option B is strongest for the discipline argument but coldest as a human scene.
A. The name in the credits. A player finishes a game they love and sees a contributor's name in the credits. That person's first open-source commit was a line in that game. They went on to work in games.
B. The repo still open at two in the morning. A solo developer pushes a commit to a public repository no one is watching. A week later, an issue. A month later, a fix. A year later, readers. The mark begins with one push to a repo nobody is watching, which turns out to be the only way a repo ever gets watched.
C. A devlog read by strangers. A design doc being read by ten thousand people the developer will never meet. Most will never play the game. A few will. A smaller few will tell everyone they know.
Recommendation: Option B returns the reader to themselves, matches the stated emotional centre. Likely right call.
Six distinct passes, each independent.
Exact backer count and dollar amount at campaign close (late 2014). What Team Cherry published publicly before the campaign. Update cadence during and after. Backer language describing why they backed. Team Cherry interviews naming the campaign period as relationship-building. Sources: Kickstarter page archive, Team Cherry blog archive, r/HollowKnight, Edge/PC Gamer/Eurogamer profiles.
Quantify Stardew Valley's public-development period. Forum post count, years, specific feedback that changed the game. Dwarf Fortress: Bay 12 monthly reports, Patreon history, Steam release relationship built through two decades. Caves of Qud Patreon and blog. Sources: ConcernedApe's Chucklefish forum thread and tumblr, bay12games.com monthly reports, Freehold Patreon, post-release retrospective interviews.
First Friday Facts post date. Total count. Specific posts that admit failure or reversed decisions. Factorio's sales trajectory relative to blog growth. Same angle on Celeste: what Maddy Thorson published, when and why the source code was released. Sources: factorio.com/blog archive, Wube/Kozelek interviews, Thorson's Tumblr/Bluesky, open-sourced Celeste repo, EXOK interviews.
Mindustry's Steam revenue despite GPLv3. Shapez and Shapez 2 commercial numbers alongside open-source availability. Contributor counts on Godot and Blender, notable commercial games built on each (Brotato, Dome Keeper, Cassette Beasts, Road to Vostok for Godot). Developer statements on why the open model worked. Sources: Anuke interviews, Mindustry GitHub, tobspr Games blog, Godot Foundation reports, Blender Studio publications.
Pieter Levels' public revenue history. Buffer's open-salaries posts and stated reasoning. Indie Hackers origin via Courtland Allen's public notes. Moments that crystallised build-in-public as a method. Torvalds' 1991 Usenet post as founding document of public development. Sources: levels.io, buffer.com open-blog, indiehackers.com, the Torvalds post.
Steam release volume 2024-25 via SteamDB. Zukowski's marketing realism on wishlist thresholds and discovery. 2023-25 layoff totals as factual backdrop. None of this material occupies more than a paragraph in the final essay; it is stage-setting. Sources: SteamDB release stats, howtomarketagame.com, gameindustrylayoffs.com, GDC 2024/2025 state-of-the-industry talks.
"Someone will steal my idea." Ideas are abundant; execution, taste, and community are not. A stolen design doc is a stranger's homework assignment, not a competitor's launch. The person publishing the design doc for eighteen months has the readership that grew up with it.
"Players do not care how a game was made." Most do not. Some do, and those some are exactly the audience a new indie needs: the first hundred readers who become the first thousand buyers. A launch on an empty store page needs everyone. A launch on a page with three years of posts behind it needs only the people who were already there.
"Showing the work shows the failure." Yes. That is why it works. Factorio's Friday Facts document backtracked features. Dwarf Fortress's updates include decades of bug-fix confessions. The honesty is the moat.
"Open source does not pay." It pays for Anuke. It pays for tobspr. It paid for Godot's foundation and Blender's studio model. It pays for Bay 12 and Freehold through Patreon, for Wube through Steam. The evidence is specific and recent.
"The risk is too high for a solo developer with no safety net." The risk of silence is higher. A closed project that fails leaves the maker with a private repo. An open project leaves a readership, a record, a reputation, a history of the problem being worked on, and the first audience for whatever comes next.
- Open Development as the Path for New Indies
- Making a Mark in the Open
- The Work, Shown
- Transparency as an Indie Advantage
- How a New Indie Is Found
Recommendation: Title 2 carries the central image cleanly. Title 1 is most descriptive. Title 3 is the quietest and most Volley!-register; pairs best with Closing Option B.
Contributing
The game
The Cast
Process
Reference