<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[How We Prioritize Features]]></title><description><![CDATA[<h3>See our public roadmap <a href="https://trello.com/b/CBCpQu8p/public-roadmap" rel="nofollow ugc">here</a>!</h3>
<p dir="auto">RollTogether was built based on the feedback we've received over the years moderating <a href="https://www.reddit.com/r/lfg" rel="nofollow ugc">/r/lfg</a> and likewise the community here will help shape the future of the platform. We want to solve real problems in the TTRPG space while keeping the platform easy to use and sustainable. We ask that users of RollTogether use this category to submit ideas they think will help improve the platform and the lives of their fellow players and GMs.</p>
<p dir="auto">When you submit a feature request, it's visible to the community: they can discuss it and vote on it. Votes and discussion help us understand which problems matter most to the community. The RollTogether team will review these requests and, if we think it aligns with RollTogether's goals and is worth exploring further, we'll pull it into "exploring." During exploration, we'll discuss the feature internally to see if it's technically feasible and refine the idea. If, after that discussion, the feature still looks good, we'll write it up and move it into "planned," which means we intend to work on it, but don't guarantee a specific timeline. Once we have bandwidth to work on the feature, it'll be pulled into development ("Currently Building") until complete and tested. It should be noted that we're usually going to prioritize fixing bugs and other broken functionality over adding new features, so it may take some time to move from planned to building. We appreciate your patience as we work to build features thoughtfully and sustainably.</p>
<p dir="auto">Our evaluation process for feature requests asks a few questions:</p>
<ol>
<li><strong>Does it help people find and play TTRPGs?</strong> This is our guiding principle. We're going to prioritize features around better matching, easier discovery, improved application, and better GM/player workflows.</li>
<li><strong>Does it improve safety and trust?</strong> We know abuse is a problem in this space. We're interested in building things like better reporting workflows, anti-spam measures, moderator tools, and privacy improvements.</li>
<li><strong>Does it solve a common problem?</strong> Features requested by many users or that solve a significant problem are going to be prioritized over niche requests.</li>
<li><strong>Is it feasible?</strong> We're a small team building RollTogether alongside our day jobs, so we have to be thoughtful about where we invest our time. If a feature requires too much development effort, maintenance costs, or technical complexity, we may deprioritize that feature, even if we think it's cool.</li>
</ol>
<p dir="auto">Some ideas may <em>not</em> fit RollTogether's goals. For example, features that encourage popularity contests, public ratings or judgments of individual players, or behavior that makes the community feel less welcoming are unlikely to be priorities.</p>
<p dir="auto">So, if you have an idea that you think will make RollTogether better, create a new feature request. Answer the questions in the template thoroughly, explaining the problem with how things are now and how your suggested change will make things better. The best feature requests focus on the problem you're trying to solve rather than the solution you have in mind.</p>
<p dir="auto">RollTogether exists because, even with the LFG sub, finding the right TTRPG group can be difficult. Thanks for helping us build something that makes that easier.</p>
]]></description><link>http://forum.rolltogether.app/topic/2/how-we-prioritize-features</link><generator>RSS for Node</generator><lastBuildDate>Fri, 04 Sep 2026 02:01:22 GMT</lastBuildDate><atom:link href="http://forum.rolltogether.app/topic/2.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 07 Jul 2026 17:45:06 GMT</pubDate><ttl>60</ttl></channel></rss>