New UI - Add viewing time

Hello there,

In the new UI on Android, I’ve lost the viewing time display in the history. The little tag with the date (or just “today” or “yesterday”) is fine, but the exact time is missing, which is entered when you add the movie/show as watched. I use tracking very precisely, and I would like the time to be added to the tag, please (e.g. “Today, 22:30” or “5 January 2023, 15:45”).

Also, I can no longer find the personal notes I had written on a lot of films and/or series. Has this feature been removed?

Finally, I have the impression that with the new star rating system, you cannot delete your rating. Pressing the star again only deducts 0.5 points.

Thank you in advance for your reply.

Actual times should be on the radar, at least, thanks to comments on New history page · Issue #1408 · trakt/trakt-web · GitHub

Notes are not implemented at present. Web interface is tracking that (Bring back Notes · Issue #1540 · trakt/trakt-web · GitHub) and they will probably return to Android shortly after web.

Removing ratings is implemented in web (feat(rating): adds support for removing ratings · trakt/trakt-web@bd64920 · GitHub) — but unclear if that feature will come to Android. I’m not good with Kotlin, but I couldn’t find any code that looks like it does that yet.

2 Likes

There’s also an issue in the Android repo for removing ratings

Why didn’t you link it?

I checked android issues first but could not find anything related. The issue didn’t exist until about 7 hours after my previous post. Ratings -> Remove rating · Issue #51 · trakt/trakt-android · GitHub

Enhancements and feature requests that wouldn’t be Android or iOS specific should flow from web to mobile. This at least is our internal policy.

You, as a user, can open issues on any repository. We’ll triage them. If it’s something we want to do on all platforms, the issue will first exist and be dealt with on trakt-web. When the “experience” is ready on web, it will be ported to the Android and iOS repo. This also means issue creation if it doesn’t exist yet. This is what happened here.

TLDR: don’t be surprised if a GH issue is a bit behind on Android or iOS, it will get there eventually.

Hope this clarifies things.

1 Like

It does clarify, thanks.

My project-management style would open the planning issues downstream much sooner (when committing to implement the feature upstream, not after finishing it) and mark them as blocked by the upstream one until it’s closed (finished). But I can accept that not everyone is that keen on proactively setting up a chain of issues and their relationships.