Skip to main content
Question

Feature Request - Feature requests board

  • November 4, 2025
  • 2 replies
  • 39 views

Forum|alt.badge.img+1

Hi RevenueCat Team,

I'd like to suggest an improvement to the feature request process.

From what I've observed, new feature ideas are currently posted as regular forum topics. While the team is responsive in acknowledging them, the threads are often closed after the request is "forwarded to the team."

This process can feel like a bit of a black box for users. We don't have a way to see if a feature is being actively considered, its priority, or an estimated timeline. I personally suggested two features about a year ago, and the lack of a clear status update makes it discouraging to contribute new ideas.

I propose creating a dedicated feature request portal/page. A system like this would be a huge win-win:

  1. Prioritization: It would allow users to upvote and comment on requests, giving your team a clear signal of what the community needs most.

  2. Transparency: A status (e.g., "Planned," "In Progress," "Released," "Won't Do") would keep everyone informed and manage expectations.

  3. Centralization: It would create a single, open place for discussion around new features, rather than scattering them across forum posts.

This would not only provide your team with more structured, actionable feedback but also make users feel more heard and invested in the product's future. And what’s most important, eventually the product would be better.

Thanks for considering this.

This post has been closed for comments

2 replies

chris_perriam
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • November 8, 2025

Hi ​@julia-835be2, thanks so much for sharing this. Acting on feedback from our users has always been a key part of our success, and we absolutely are focused on continuing to do so.

We have a robust process internally which captures feedback from social media, our online community, customer interviews, in-person events, emails and support tickets. While every item of feedback is considered and discussed internally (including this), unfortunately we’re unable to act on everything.

With feedback submitted on in our Community, members are able to upvote threads even if they have been automatically closed for inactivity. If threads have been tagged “Feature Request”, they’re able to be found here: https://community.revenuecat.com/search?q=Feature%20Request&search_type=tag


Also worth mentioning - we’ve created a new Changelog page on our website where customers can keep up-to-date with the latest significant changes we’re shipping: https://www.revenuecat.com/changelog


Forum|alt.badge.img+1
  • Author
  • New Member
  • November 12, 2025

Hi ​@chris_perriam , thanks for the detailed response. 

I think that looking for feature requests somewhere in the community posts is not the best UX.
I’d say it doesn’t really encourage to go through feature request and upvote unless I’m looking for something specific. It’s also harder to spot what’s most important for users as default sorting is by the date, while on feature request page it’s usually by the number of votes.
Seems like the easiest UX improvement that you could make is just another tab in the community page.
Currently there are tabs like “SDKs”, “Dashboard & Tools”, “Third party integrations” and “General Questions”. Adding another tab “Feature request” with sorting by number of votes seems like an easy win-win.
Just a suggestion though :)

Cheers