Skip to main content

Invest substantially more time/energy/manpower into realising requested features

Feature Request

This site is a good place for Trakt users to provide meaningful suggestions. However it’s effectiveness depends on what is subsequently done with those suggestions.

According to the Public Roadmap, there is a backlog of 340 (and growing) suggestions, issues and feature requests. Many of these requested features are basic functionality that already used to be on Trakt V2, but are no longer there in Trakt V3. On the other hand there is an active number of 3 (!) issues currently in progress.

Based on that it seems currently (almost) nothing is being done with the many valuable suggestions that have been made. Is that conclusion accurate? And wouldn’t it be a good idea to invest substantially more time/energy/manpower into realising the many useful feature request?

Thank you!

Posted by Amnon ·
Status: Rejected1 comment

Log in to comment and vote

Comments1

  • Kevin Cador changed status to Rejected
    Team•

    Sep 3

    Pinned

    Thanks for sharing this feedback. We understand why the small number of items marked In Progress on the public roadmap could create this impression, but it doesn’t represent everything currently being worked on.

    Featurebase is where we collect and organize feature requests, and the public roadmap is built from those requests. It isn’t intended to be a complete view of our development backlog or day-to-day activity.

    Our ongoing work can be followed through the Trakt organization on GitHub (a lot of our repositories are open source, including the main web frontend). A substantial part of the backlog remains there, spread across several repositories covering the website, mobile and TV apps, backend services (not open source), API, infrastructure (not open source), and other projects.

    We do acknowledge the broader concern: users understandably want to see meaningful progress on the requests and missing functionality that matter to them. Votes and feedback here help us understand those priorities, alongside technical requirements, impact, dependencies, and the work already tracked on GitHub.

    I’m marking this post as Rejected because it is general feedback about prioritization and resourcing more than a specific product feature we can scope and implement. That doesn’t mean the concern is being dismissed → it remains heard and acknowledged. Thank again for your feedback!