Quick answer: Twitter/X retains one unique asset — the game industry's professional graph: press, publishers, festival scouts, and fellow devs still discover games there. Its consumer reach and link distribution have deteriorated badly. The right-sized strategy: keep a presence as a portfolio and networking surface, post your best clips and milestones, but spend your consumer-marketing hours on channels that still deliver them.

Twitter/X retains one unique asset — the game industry's professional graph: press, publishers, festival scouts, and fellow devs still discover games there. Its consumer reach and link distribution have deteriorated badly. The right-sized strategy: keep a presence as a portfolio and networking surface, post your best clips and milestones, but spend your consumer-marketing hours on channels that still deliver them. That's the short version — the sections below get into the how, the why, and the mistakes worth dodging.

What the platform still uniquely has

The industry never fully migrated: journalists scan it for stories, publisher scouts follow gamedev hashtags, festival organizers and fellow devs trade visibility there. Indie success stories still begin with a clip that circulated through that professional graph — retweeted by a big account into press coverage. For B2B-shaped luck (coverage, deals, collabs), the network effect persists.

That makes the account a professional artifact: pinned post showing your game at its best, bio with the Steam link, a feed that demonstrates momentum. Scouts who hear about you will look — what they find should sell.

What it no longer does well

Organic consumer reach has thinned: link posts are suppressed, follower feeds are diluted by algorithmic content, and engagement on median dev posts has fallen industry-wide. The consumer discovery that drifted to TikTok, YouTube, and Discord isn't drifting back. Treating X as your primary wishlist engine in this era is fishing a drained pond.

The audience question is also genre-specific: some communities (certain strategy, retro, and dev-adjacent niches) remain active; check whether games like yours still find traction before investing.

The right-sized routine

A sustainable posture costs an hour a week: share your best clip or milestone (cross-posted from your other channels — marginal cost zero), engage genuinely with your genre's dev community, and join the recurring visibility rituals (screenshot-sharing days still circulate work). Skip what no longer pays: link-spam, thread-strategy theater, and chasing the algorithm with volume.

Diversify the same content across the successors too (Bluesky's gamedev scene is lively and press increasingly watch it) — the cross-posting pipeline makes presence-everywhere cheap, and you want to be findable wherever your particular luck strikes.

Marketing is a generosity game

The indie marketing that works rarely looks like advertising. It looks like sharing something genuinely interesting: a clip that makes people grin, a devlog that teaches something, a thread about a problem you solved. People share what makes them look good for sharing it.

So lead with the most interesting true thing about your game, not with the ask. 'Wishlist now' earns nothing by itself; a great 15-second clip earns the wishlist without asking twice.

Consistency compounds, virality doesn't

Every indie knows one game that blew up from a single tweet, and that story wrecks more marketing plans than it helps. Viral moments are lottery tickets. The reliable curve is slower: post regularly, get a little better each time, and let followers accumulate like interest.

Pick a cadence you can sustain on your worst week — one post, one clip, one devlog — and hold it for months. The audience you build that way actually shows up on launch day.

Plan for the bugs you won't see coming

Whatever else you take from this, build yourself a way to hear about problems. Once your game is on other people's machines, most failures happen out of sight: the crash on hardware you don't own, the save that corrupts once in fifty exits, the bug players mention in a review instead of a report.

A lightweight crash and bug reporting setup — even just Bugnet's free tier wired into your engine — turns that silence into a fixable list. The devs who look calm at launch aren't luckier; they just see their problems earlier.

Putting it to work

Don't try to act on all of this at once. Pick the one change that costs you the least and pays the most this week, do it, and see what actually happens before reaching for the next.

Most of this rewards steadiness over intensity. A small improvement made every week, checked against how real players respond, outruns any single burst of effort — in this corner of game development and every other one.

Show up where your players already are, lead with the interesting thing, and keep the cadence.