All other criticism aside, this is especially amusing to me. I was a software dev at Warner Bros. during the merger with Discovery, and literally the entire system was replaced with a ground-up rebuild to integrate the two services. Code, servers, infrastructure, deployment process, tools, everything, brand new. After proper development and testing, we had the whole thing cut over in a couple days with only one or two very minor issues. Most people never saw even a blip in their streaming activities or account sessions.
Now granted, WBD is orders of magnitude bigger than Trakt with far more resources, but that also means Trakt has orders of magnitude fewer issues to deal with and customers to transition. More importantly, this just points to a bad release strategy. Most of the problems and missing features were known before the forced cut to V3. I could understand some bugs or whatever, but knowingly moving forward before the product was ready can’t really be dismissed with an excuse like “these things take time”. I mean, yes, development takes time, but that’s why you do it behind the scenes BEFORE releasing it.