Roadmap and Feature Requests
FeedbackOS is actively developed - and user feedback plays a central role in shaping what gets built. This article explains how feature requests work, how prioritisation decisions are made, and what you can look forward to in the future!
How to Request a Feature
All feature requests and product suggestions are tracked publicly on the feedback site:
If you have an idea, suggestion, or improvement in mind, please submit it there rather than by email for ease of tracking. FeedbackOS was created with exactly this goal in mind - and it really will be easier for FeedbackOS ideas to be found, tracked, and acted on if they're posted there.
Subscribing to Suggestions
You can subscribe to any existing suggestion to signal that it matters to you.
Subscribing helps in two important ways:
- It indicates how many users are interested in a particular idea
- It allows you to receive updates when there is progress or discussion
Subscriptions are an important signal when prioritising work - but they are not the only factor considered.
How Prioritisation Works
When deciding what to work on next, a number of factors are considered - such as:
- The number of users subscribed to a suggestion
- How broadly useful the change would be
- Alignment with the product’s long-term direction
- Technical complexity and ongoing maintenance cost
- Impact on reliability, security, and performance
A suggestion with fewer subscribers may sometimes be prioritised over a more popular one if it is foundational or unlocks future improvements.
What the Roadmap Represents
Items marked as planned, under consideration, or in progress reflect genuine intent - not guarantees.
Keep in mind that timelines can shift due to:
- Technical discoveries
- Security or infrastructure work
- Regulatory or compliance considerations
- Bug fixes or stability improvements taking priority
For this reason, the roadmap should be read as a directional guide, not a fixed delivery schedule.
Why Some Suggestions May Not Be Implemented
Not every suggestion will be added to FeedbackOS.
Core goals of FeedbackOS are that it continues to be:
- Simple to use
- Affordable
- Focused on its core purpose
Suggestions that would significantly increase complexity, cost, or support burden - especially if they benefit only a small subset of users - may be feasible.
Where possible, decisions and reasoning will be shared publicly on the relevant suggestion.
Bug Reports vs Feature Requests
Bug reports should also be submitted via meta.feedbackos.net, clearly marked as bugs.
This helps ensure issues are:
- Visible to other users
- Tracked properly
- Updated transparently as progress is made
For account-specific or payment-related issues, please email support@feedbackos.net.
Staying Informed
Updates to suggestions and roadmap items are posted on the feedback site itself. Major changes or launches may also be reflected in product updates or release notes.