THE INDIE GAME DEV SUBREDDIT: COMMUNITY GUIDE

I posted a GIF of my first game's physics system to r/indiedev about three years ago. Got twelve upvotes. One comment: "cool." That was it. I spent an hour picking the perfect three-second clip, tweaking the resolution, writing what I thought was a compelling title, and the internet gave me the equivalent of a polite nod. The next week I posted the same GIF to r/gamedev with a paragraph explaining the technical problem I was solving, and it got 400 upvotes and a thread full of people asking about my collision detection implementation.

Same content. Different community. Completely different result. That experience taught me more about how Reddit's indie dev communities actually work than any guide I'd read at the time.

The big ones and what they're actually for

r/gamedev is the largest game development subreddit, sitting at over a million members. It's not specifically for indie devs, but most of the active posters are indie or hobbyist developers because the AAA folks are under NDA and can't talk about anything. The culture skews toward discussion and advice over self-promotion. Technical questions do well. "How do I structure my save system" posts get genuine engagement. Marketing screenshots with no context get downvoted into oblivion.

r/IndieDev (capital I, capital D, and yes, the capitalization matters for finding it) is the more relaxed cousin. It's friendlier to self-promotion. You can post a trailer or a screenshot of your game and people will generally be supportive. The flip side is that the feedback tends to be surface-level. "Looks great!" is nice to hear but it doesn't tell you that your UI is unreadable or your character animations look stiff. r/indiedev (lowercase) redirects to the same place now, but you'll still see both referenced in guides and old posts, which creates confusion for newcomers.

r/solodev is smaller and more focused. If you're making a game by yourself, this is probably the most relevant community. The vibe is more intimate. People recognize each other's projects. You can post progress updates over months and build a genuine following within the subreddit. The smaller audience means less exposure but more meaningful interaction.

r/devblogs is exactly what it sounds like. Development blogs, progress posts, behind-the-scenes content. It's a good place to cross-post longer-form updates that might get buried on the bigger subreddits. Traffic is lower, engagement is lower, but the people who are there actually want to read development content rather than just scroll past it.

There's also r/playmygame for when you have something playable, r/DestroyMyGame for when you want brutally honest feedback (and I mean brutal), and r/gamedesign for theoretical discussions about mechanics and systems rather than specific projects. Each one fills a niche, and knowing which niche is which saves you from posting the wrong thing in the wrong place.

The unwritten rules nobody tells you

Every game dev subreddit has the same implicit social contract: participate before you promote. Reddit communities can smell a drive-by self-promoter from miles away. If your entire post history is links to your own game with zero comments on anyone else's work, you're going to have a bad time. Most subreddits have a formal self-promotion ratio in their rules (usually 10% or less of your posts should be your own content), but the real standard is vibes-based. People check your profile.

I spent about a month just commenting on other people's posts before I shared anything of my own. Answering questions about Unity. Giving feedback on people's art. Asking genuine questions about approaches I didn't understand. When I eventually posted my own work, I wasn't a stranger showing up with a sales pitch. I was someone people had seen around.

The other unwritten rule: lead with something interesting, not just "here's my game." A screenshot of a forest environment with the title "Working on my survival game!" is invisible. Reddit has trained its users to scroll past generic content. But "I spent a week writing a shader that makes trees sway based on actual wind simulation data, here's how it looks" gives people a reason to stop and pay attention. The content can be identical. The framing changes everything.

Don't just drop your Steam link and vanish. I've seen this kill potential conversations dozens of times. Someone posts a genuinely interesting mechanic, someone in the comments asks a technical question, and the original poster never responds because they were never planning to stick around. That comment section dies, and so does any goodwill toward the project.

Common mistakes I've seen (and made)

Posting too early is the classic one. You have a gray box moving across a screen with programmer art, and you're excited because you just got your movement system working. That's great, and you should be proud of it. But reddit doesn't care about your gray box. The minimum bar for visual content that gets engagement is higher than most new devs expect. You don't need polished final art, but you need something visually coherent enough that a person scrolling at speed will pause on it.

Posting too often is the other side of it. If you're posting a new update every two days, people start ignoring you. I've watched developers post daily for weeks, getting diminishing returns each time, then conclude that "Reddit doesn't work for marketing." Reddit works fine. They just fatigued their audience. Once a week at most for the same project. More than that and you're spamming, even if each individual post has new content.

Asking for feedback but not actually wanting it is a subtle one. Someone posts "What do you think of my game's art style?" and when people give honest criticism, they get defensive in the comments. If you're not prepared to hear that your character designs look generic or your color palette is muddy, don't ask. Post it as a showcase instead. There's no shame in just wanting to show off your work. The problem is framing it as a feedback request and then arguing with the feedback.

The title game matters more than people realize. I've seen the same developer post the same content twice with different titles, and the results were wildly different. Specific, technical, or surprising titles outperform generic ones every time. "My indie RPG" loses to "I made an RPG where every NPC remembers how you treated them and gossips about it to other NPCs." Both describe the same feature. One makes you want to click.

The feedback problem

Here's something I've been thinking about for a while. Reddit game dev communities are good at telling you what's wrong with your game. They're not good at telling you whether your game will sell. These are fundamentally different questions, and confusing them leads to bad decisions.

A post that gets 2,000 upvotes on r/indiedev does not mean you have a commercially viable game. I've seen gorgeous, highly-upvoted projects launch to crickets on Steam. Reddit developers are not representative of the game-buying public. They appreciate technical craft, unique art styles, and clever mechanics because they understand the work behind them. Regular players just want to know if the game is fun and if it's the kind of fun they're looking for. This matters even more when you start looking at the real costs of indie game development and realise upvotes don't pay for rent.

Conversely, a post that gets ignored on Reddit doesn't mean your game is bad. Some genres just don't perform well on these platforms. Casual games, mobile games, puzzle games without a visual hook, management sims that require explanation to understand their appeal. These can be perfectly viable commercial products that Reddit simply doesn't get excited about. If your feedback strategy relies entirely on Reddit upvotes, you're optimizing for the wrong audience.

The most useful feedback I've gotten from Reddit wasn't from showing my game. It was from reading the criticism on other people's games and asking myself if the same problems applied to mine. You learn faster by watching how communities respond to work similar to yours than by posting your own stuff and waiting for validation.

The echo chamber thing

I want to be honest about this because I think it's important. Game dev Reddit has a survivorship bias problem. The success stories that reach the front page are the outliers. "I quit my job and made a game and it sold 100,000 copies" gets massive engagement. "I quit my job and made a game and it sold 200 copies and I went back to my job" does not. Both outcomes are real, and the second one is much more common, but the community's content naturally amplifies the wins and buries the losses.

This creates a distorted picture for people just starting out. The implicit message is that if you work hard enough and make something good enough, success will follow. That's not wrong exactly, but it leaves out the part where marketing, timing, platform algorithms, wishlist strategies, and blind luck play enormous roles. "Just make a great game" is the game dev equivalent of "just be yourself" as dating advice. It's technically true and practically useless.

There's also a tendency toward groupthink on certain topics. Say anything positive about Unity in the months after a pricing controversy and you'll get buried. Suggest that Godot might not be ready for a specific use case and watch the downvotes roll in. These communities have their own tribal loyalties, and going against the grain takes more courage than it should on a forum ostensibly about sharing knowledge.

I'm not saying this to discourage anyone from participating. I still post and comment on these subreddits regularly. But going in with realistic expectations about what the community can and can't give you makes the experience much better. Use Reddit for technical discussion, for finding people working on similar problems, for early visual feedback, and for staying connected to the broader indie dev world. Don't use it as your primary measure of whether your game is worth making.

Getting actual value out of it

The best thing Reddit's indie dev communities offer isn't visibility for your game. It's access to thousands of people solving the same problems you're solving, in real time, for free. The technical threads on r/gamedev have saved me weeks of work. Someone asking "how do you handle inventory systems for games with hundreds of item types" generates responses from developers who've actually shipped games with that exact problem. That's gold. No tutorial, no GDC talk, no blog post competes with a specific answer to a specific problem from someone who just dealt with it.

r/DestroyMyGame deserves special mention here. It's the only subreddit where the explicit purpose is honest, harsh feedback. People post their Steam page or trailer and ask the community to tear it apart. The responses are blunt. "Your trailer is 90 seconds too long." "I have no idea what genre this is from looking at your page." "The name is unpronounceable and unsearchable." This kind of feedback is uncomfortable and incredibly valuable. If you can handle it, post there before you launch. Better to hear that your store page is confusing from Reddit strangers than to figure it out from your sales numbers.

For actual community-building and long-term engagement, pick one or two subreddits and become a regular. Comment on other people's work. Answer questions when you can. Share what you're learning, not just what you're making. The developers I've seen build genuine audiences on Reddit all did it the same way: they showed up consistently, contributed to conversations that had nothing to do with their own projects, and let their game promotion be a small percentage of their overall activity.

It takes longer than just blasting your trailer everywhere. It works better. And honestly, it's more fun. Talking to other developers about shared problems is one of the few parts of indie dev that doesn't feel like work. The subreddits are good for that, even when they're not good at predicting which games will sell.