Change is a process. Trakt v1 started in 2010 and was written in PHP. By the end of 2014, the site basically became unusable due to the architecture and how the site was hosted. We were already working on a complete rewrite for v2 in Ruby on Rails. Plans accelerated (v1 was crashing daily) and we had to launch v2 way ahead of schedule, missing a ton of features and with bad performance.
Over the next few months, we worked to implement and improve the site a ton. It wasn’t a fun couple of months for me personally, based on community reactions and unconstructive feedback (that’s putting in nicely 
). But we worked through it and v2 became a strong baseline for the next decade.
We’re in a different place today. New Trakt (codename v3) does not have feature parity with v2, Kevin made that clear in many of his posts. However, v2 still exists and can be used while v3 matures. The 2014 transition didn’t have that luxury.
I am the primary developer on v2 and while in maintenance mode, that means I’ll continue making bug fixes and performance updates. It also means that v2 won’t get any major new features. I have some personal obligations in December and January, so my time and responses will be limited.
We’ll address all the pain points with v3. It will be a process, a multiple month or maybe year process. My suggestion is to think of “scenarios” rather than just “features”. A lot of features are missing in v3, but if we think in “scenarios” that helps us develop and prioritize the features for v3. Some features will be ported over, others will be simplified, others might be new concepts, some might be dropped.
Trakt has real people working behind the scenes, we aren’t just outsourcing things to AI (except community sentiments 
). We are working around the clock (we’re all in different time zones after all) and putting in the daily effort. The new design takes center stage, but there is so much more going on behind the scenes. The v3 platform is globally distributed, localized, and built to scale.
Sean is working with the design team to revamp the desktop mode, since you’re right it was developed as mobile/tv first without desktop getting the love. List management will be back. Stats will be back.
All I ask is to be respectful with your comments and check in over the next year to see if your must have scenarios have made it to v3 yet.