Best practices / for indie developers

Build a community

Best practices for giving interested players a reason to return, sharing useful updates and gathering feedback without promising a constant content stream.

Start hereHow to grow a Discord server for your game →

Choose a useful next step.

Start with the reason someone would join and what your team can maintain. The Discord guide is the dedicated starting point in this collection.

  1. Choose a clear purpose

    Decide whether the space is for feedback, playtest coordination, updates or discussion.

  2. Plan the work involved

    Allow for moderation, useful information and replies before opening another channel.

  3. Connect it to the game

    Use a devlog or playtest when it serves the same purpose. They are linked as related reading below.

The dedicated guides

Read the guide for your next step.

Related reading

Devlogs can help you decide what is worth sharing. Steam Playtest covers a different job: learning from people playing a build. Both belong to their own collections and are linked here when that job fits.

Useful across all five areas

The shared foundations.

← All best practices