February 4th, 2026
A lot happened this month 😅
Stepping back, we can say January was about clarity, direction, and improving trust.
We spent the month explaining where Trakt is going, clearing up misconceptions, and opening up more of our process so expectations are clearer on all sides. This is an ongoing process, and we’ll continue to share more as we move forward.
We started the month (and the year) by sharing the next generation of Trakt on mobile. This is the strong foundation that will allow faster iteration, more consistency across platforms, and fewer compromises over time.
📱 A New Chapter for Trakt on Mobile
We clarified what the Library is meant to represent in the near future and how it fits into the broader Trakt experience.
In short, the Library will be about media you can actually play, not a general-purpose archive. That distinction matters as we expand integrations and improve playback-related workflows.
📚 The Library on Trakt: What It Is and Where It’s Going
January also saw the release of 10 Myth Busters, addressing recurring assumptions and concerns we see across the Forums and Reddit.
The goal wasn’t to win arguments, but to provide context, explain decisions, and reduce confusion where possible.
We read a lot of messages on the Forums, on Reddit, and shared with support, far more than we can realistically respond to one by one.
When we don’t reply, it doesn’t mean feedback is ignored. It usually means we’re managing volume, time, and priorities as a small team. Themes, patterns, and actionable feedback are still actively shared and acted upon internally.
We also want to say thank you to everyone helping out there. Seeing Trakt users debug issues, explain behaviors, and share recommendations with other Trakt users genuinely makes us happy!
We see you and appreciate your contributions 💜
We started publishing weekly, more comprehensive release notes for the Web (V3) platform to improve visibility into ongoing changes and fixes.
Web release notes are now available alongside iOS and Android release notes under the release-notes category. Unlike mobile apps, the Web is updated continuously and doesn’t use version numbers, so these release notes follow a slightly different format.
🛎️ Make sure you’re “watching” these posts to get notified of new updates!
Trakt for Web: Trakt for Web 🌐
Trakt for iOS: Trakt for iOS 🍎
Trakt for Android: Trakt for Android 🤖
In January, we also started the big move from an internal project management tool to GitHub as part of our ongoing effort to build more in public.
This means you can now:
Submit bug reports and feature requests using our structured templates
See priorities, assignees, status, and even some internal discussions and sneak peeks
Track progress through Milestones for larger features or versions
Repositories and open source status:
Web V3: has been open source from the start → trakt-web
Android V3: the source code was made public this month → trakt-android
iOS V3: the source code remains private for the moment but issues and progress has been opened → trakt-apple
In January, we shared some upcoming API changes that will have an impact on third-party developers:
For all, even non-developers: we work hard to keep breaking changes to a minimum, but some adjustments are necessary to ensure Trakt can scale reliably as our user base continues to grow.
All breaking changes, behavior changes, and important API announcements are shared via GitHub Discussions in the trakt/trakt-api repository.
To make sure you don’t miss updates:
Watch → All Activity
or Watch → Custom → Discussions
Keeping GitHub notifications enabled is the best way to stay aligned.
January was about setting expectations, explaining direction, and improving how we communicate, while continuing work across Web, iOS, Android and the Platform (API, Database, Infrastructure,...) in parallel.
Thanks for the continued feedback and support.
🍿 The Trakt Team