There is no database - your Trakt credentials only exist in your encrypted session cookie.
It’s completely AI-generated. If you spot issues or have something you want added, feel free to raise a PR or create an issue and I’ll have Claude take a look.
I would note that watch/list status when exploring the site isn’t really implemented, so open to PRs or ideas to improve that - I believe Trakt might rely on a big client-side cache for it to work . I’m sure there’s probably lots of bugs.
Vibe-coding a solution isn’t my preferred approach
Disclaimer: This project is entirely AI-generated.
Thanks but no.
You don’t have to use it if you don’t want to use things AI is involved in, I don’t particularly care
I wanted something with a nicer UX that better aligns with what I find visually appealing, and I didn’t want to spend weeks building something from scratch when I’m already struggling to find time to work on side projects during my evenings.
I think this is probably one of the better ways you can use AI, and something we’ll see more of in the future - generating personal, tailored interfaces that suit your specific needs for APIs. This was created solely to give me an interface I want, not to give others something they want, or make money from, hence why I’m not spending weeks writing it by hand. I’m only sharing it because many others express frustration with the V3 design.
Anyway, I’d rather this not be a thread on peoples’ preferences on how AI is used in the world - you can use Twitter for that.
I’m dismayed that you skipped over both my good-faith attempt to point you toward how Trakt’s own (“Classic”) frontend handles watch/list status
I’m sorry it came across like that by not replying to that part. I was already aware of how V2 handles caching data and the problems that come with it - it annoys me every single time I click to add a rating or mark something as watched on V2, to the point where I only watch/rate things in the mobile app or on Infuse and let it sync across, or wait 15 seconds before interacting
My issue with generated code isn’t so much the generation itself, but the potential (in)correctness of its output. I’d love to try out your frontend, but I’m worried about it doing unexpected things as side effects while I test it out
Yeah, this is a big issue with generated stuff when you’re not involved in the process… It’s part of the reason I ripped out the database it originally added in for auth in favour of sticking solely to cookies - one less thing to potentially go wrong and reduces the risk of tokens being stolen…
I just clicked the button because what the hell do I even care about my Trakt data anymore but I gotta say your AI coded thing already even looks better than the Trakt v3.
I gotta say your AI coded thing already even looks better than the Trakt v3
Thanks! One of the benefits of building something specific to what you want . Can design it around precisely what you think looks good rather than what the company thinks looks good for everyone!
The only thing I’m really interested in nowadays is the calendar view. So this is perfect for me. I was about to vibe code something myself, so you’ve saved me the trouble. Thanks mate.
. I’m sure there’s probably lots of bugs.
