Meeting users where they already are, starting with Discord

The community for a D&D platform is not on the platform. Not yet. It is on Discord.

This is true for almost any tool a DM uses. The session is in a Discord voice channel. The campaign chat is in a Discord text channel. The party planning, the scheduling thread, the "I cannot make it tonight" message, the joke about last week's encounter, all of it lives in Discord. If your product wants to be part of that DM's life, it has to show up where they already are.

This stretch was about getting that connection in place.

The bot is a listening post first

The first version of the Discord bot is not a feature integration. It is a feedback channel.

There is a long-term version of this bot that does what users would expect a D&D platform's Discord bot to do. Schedule the next session from a slash command. Get a heads-up when a player updates their character. Trigger a campaign event from a context menu. That bot will exist. Some of it is already starting to exist.

But the version that mattered first was simpler: give me a way to hear what users are saying without making them leave Discord to say it. The bot processes feedback. It can list tickets. It has context menu commands so a user can flag a message as feedback without breaking their flow. The architecture is deliberately thin. The bot is mostly a bridge from a Discord interaction to a row in a database that I look at later.

The reason to build it now, before there is a real community to listen to, is that listening infrastructure does not work retroactively. By the time you have enough users that you need a feedback channel, you do not have time to build one. You build it early, you let it sit mostly quiet for a while, and when the community shows up the channel is already there.

Discord is the right surface for this

The choice to put the bot in Discord, instead of building an in-app feedback widget, is not really a choice for a D&D product. It is the obvious move once you see where the conversations actually happen.

A feedback button in a web app collects a fraction of what people say about your product. People feedback in their group chat. They feedback in their DMs to the friend who recommended the tool. They feedback in the Discord server where they actually use it. The product that wants to hear that feedback has to be in those rooms.

The bot's job is to be a presence. When someone right-clicks a message and says "this is feedback for D3Designs," the bot's job is to receive that signal cleanly and put it somewhere I can read it. Eventually it will do more. For now, that is enough.

The desktop app is in motion

The other thing taking shape in this stretch is a desktop application.

Not everyone wants to live in a browser tab. The DM running a four-hour session does not want their tools sharing window real estate with seventeen other tabs, three Slack workspaces, and whatever else the browser is holding. A desktop app gives the product a dedicated home for the people who prefer it.

The app is under active development. It is not finished. The work in this stretch laid the foundation for it: a real surface that the product can ship into, separate from the web. What that surface ends up looking like, and which features it gets first, is still being figured out. The honest version is that the desktop app is an in-progress bet, not a shipped product.

What it represents, even half-built, is the same idea as the Discord bot. The product should meet the user where they want to use it. Some users want a browser. Some users want a desktop app. Some users want to interact with the product entirely from inside Discord. The platform's job is to make all of those surfaces feel like the same product.

What the stretch shipped

A Discord bot that listens. A desktop application in development. A clearer commitment to a single idea: the platform reaches out to where users already are, instead of asking them to come to a single place to use it.

There is more of this coming. The bot will grow into the campaign-facing features that DMs will actually use during play. The desktop app will land. Other surfaces, eventually mobile, will get the same treatment. None of that is fast work. All of it is the right work.

The community is not on the platform yet. The platform is being built so it can listen when the community arrives.