Most studios treat a devlog like a press release: post when there's news, go quiet when there isn't, and wonder why nobody shows up at launch. A devlog strategy for games works the opposite way. Done right, it turns the slow months of development into the engine that builds your audience, because people follow the person making the thing long before they care about the thing itself.
The instinct is to wait until something looks finished. Resist it. The content that earns follows is the messy middle: the enemy AI that kept walking into walls, the three art styles you tried before the fourth one clicked, the day you deleted a system you'd spent two weeks on. Finished features impress nobody because they look like every other game's finished features. Process is the only thing you have that's genuinely yours.
Pick a cadence you can actually sustain through a bad week, not your best week. One solid post every two weeks beats four posts in a burst followed by two months of silence. The algorithm and the human both reward consistency over volume, and a dev who vanishes for a month reads as a dev whose game is dying.
A devlog is not a single channel. It's one body of work re-cut for where people already hang out. The mistake is producing five native pieces a week; the fix is producing one substantial thing and slicing it. A ten-minute YouTube devlog becomes a 40-second TikTok of the single best moment, a before/after image pair for Reddit, a short written breakdown for your Steam community hub, and a reply-bait question for X or Bluesky.
- YouTube / long-form: the full narrative what you tried, what broke, what you decided
- TikTok / Shorts / Reels: one satisfying loop, problem-to-payoff in under a minute
- Reddit: a genuine question or a before/after, framed for the specific subreddit's culture
- Steam community hub: the written version that converts a visitor into a wishlist
- Short text platforms: the daily texture that keeps you visible between big posts
Your YouTube channel mostly reaches people who already found you. Reddit is where strangers do. But it punishes anything that smells like marketing, so the post has to earn its place: a real problem you solved, a question you actually want answered, a clip that stands on its own without a pitch. Subreddits each have their own tolerance and rhythm, and a post that lands in one will get removed in another.
This is also the hardest surface to do solo because it rewards being a known, trusted member of a community, not a drive-by poster. If you don't have the bandwidth to be present in those spaces week after week, Reddit Launch Support exists to run that channel without torching your reputation.
An audience that loves your devlog but never lands on your Steam page is a leak you're paying for in attention. Every piece should have one unmissable next step, and that step is almost always to wishlist. Wishlists are the currency Steam reads at launch, so treat each devlog as a soft ask: show the thing, then point clearly at where to follow it.
Be specific about the ask and rotate it. Not "link in bio" buried in paragraph four, but a single clear line: this is on Steam, wishlists genuinely help the launch, here's the link. People who just watched two minutes of you fixing a bug are far more willing to click than a cold visitor don't waste that warmth by hiding the door.
Vanity metrics will lie to you. A video with 200k views and zero wishlist movement told you the clip traveled but the game didn't connect. Two numbers cut through: wishlist additions in the days after a post, and returning viewers or repeat commenters. The first tells you whether content converts; the second tells you whether you're building an audience or just renting attention from the algorithm.
- Wishlist spikes mapped to specific posts which topics actually move the needle
- Returning commenters by name your real core, the people who'll show up day one
- Save and share rates over raw views saves predict intent better than likes
- Click-through from devlog to Steam page the leak you can actually plug
None of this needs to be perfect on day one. Pick one platform, commit to a cadence you can hold, and start narrating the process you're already living. When you want a second set of eyes on which channels are worth your limited hours, that's a conversation worth having before launch, not after.