A solo game developer writing as @mt_indiedev on DEV asks how much of a game in progress should be shown publicly, and where the practical line between sharing and protecting ideas should fall. The original post is available at https://dev.to/startupcafe/does-sharing-devlogs-put-your-game-ideas-at-risk-ba1.
The author describes enjoying the act of sharing: showing a scene come together, explaining a solved problem, or letting readers see how a project has changed over time. Devlogs, in this view, let a project find an audience while it is still taking shape. The hesitation comes from the same openness, since it means exposing ideas that someone else could potentially use before the developer has finished building them.
What feels safe to show and what does not
The post draws a distinction between types of progress. Lighting improvements or a new environment feel relatively comfortable to share. A particular puzzle, a story connection, or an unusual mechanic feels different, especially for a mystery game, where those details are a large part of what makes the experience worth playing. Showing how something works might reveal both the idea and the surprise intended for the player.
The author also raises the worry that someone with more time, money, or experience could see an idea, build their own version, and release it first. The post does not claim to know how likely that is, but notes that when every feature takes considerable effort, the concern is hard to dismiss.
The limits of "ideas are nothing without execution"
The common reply to copying fears is that a concept still needs design, writing, programming, art, sound, testing, and all the decisions that turn it into a finished game. The author accepts the reasoning but says it does not fully settle the question. Execution matters, yet so does the thought behind an interesting premise or a designed puzzle, and being told the idea has little value until it is finished can feel dismissive of that work.
The cost of staying quiet
Waiting until release would remove the need to judge what is safe to show, but it would also give up feedback, contact with other developers, and early introductions to the game. The author does not want every post to become an exercise in worrying about who might be watching.
A possible middle ground is suggested: a devlog can show atmosphere, work, and challenges while leaving the central story and the most distinctive puzzles unexplained. The post admits this sounds reasonable in principle and is harder to apply post by post.
Open questions for other developers
The author closes by asking whether others have worried about copying, whether they have experienced it or mostly received useful feedback, which parts of their games they deliberately keep private, and whether they would share throughout development or wait until closer to release.