Boardssey runs a public roadmap and a feature request portal so you can see what's coming next and add your own ideas. Many features in the app today, small and large, started as designer requests.
What this page helps you do
See what we're working on now and what's coming.
Submit a new feature request.
Vote on requests other designers have made.
Where to find the roadmap
The roadmap link is in the app (sidebar → Help or similar) and at boardssey.com. Click through to see:
Now: what we're actively working on.
Next: the queue of things planned for the coming months.
Considering: things we're thinking about but haven't committed to.
Shipped: recently completed items.
The roadmap moves; what you see today is a snapshot, not a contract.
Submit a feature request
In the same portal, click Submit a request (or New idea). Fill in:
Title: short summary of what you'd like.
Description: what problem this solves for you, ideally with a concrete example. "In playtests, I want to log player count per session so I can filter feedback by group size" is much more actionable than "better playtest analytics."
Tags / category: if available, pick the area (Games, Pitches, Tools, etc.).
Submit. Other designers can vote on your request, and the team reviews new submissions regularly.
How requests get prioritized
Roughly, in order of weight:
How many designers are blocked: if a missing feature stops people from doing real work today, it's near the top.
How many designers asked: a request with 50 votes carries more weight than one with 1.
Strategic fit: does this fit where Boardssey is going as a product?
Implementation complexity: sometimes a small request gets done fast; sometimes a big one waits because it requires foundational work.
We don't promise everything will ship, and not everything should ship, but high-vote, high-impact items consistently move forward.
What "shipped" looks like
When a feature ships:
It moves to the Shipped column on the roadmap.
It appears in the next monthly What's new post.
The original requester is sometimes called out in the notes if the request was clearly the source.
What we don't take through the public roadmap
A few things go through other channels:
Bug reports: use the in-app chat bubble (see Contacting the Boardssey team).
Account / billing issues: same.
Confidential or sensitive requests: email [email protected] directly.
The public roadmap is for things you're comfortable talking about in public.
Tips & common questions
My request is similar to an existing one. Vote on the existing one rather than creating a duplicate. Add a comment with your specific angle if it's slightly different.
My request was marked "won't do." Why? Sometimes requests don't fit Boardssey's direction. We try to explain when that's the case. Common reasons: feature better suited to a specialized external tool, conflicts with another planned feature, serves a tiny audience.
Can I see the roadmap without an account? Yes, the public roadmap doesn't require a Boardssey account to view. Submitting requests typically requires sign-in.
Why isn't [obvious feature] on the roadmap? If it's missing and you'd value it, submit a request. We add to the roadmap based on real demand, not what we think people might want.
Related articles