Navigate to screensaver item via button press

[grunwalski]

This request respects the following points:

• This request is not already on GitHub (I've searched it).
• I agree to follow Jellyfin's Code of Conduct.

Problem description

If you want to watch - or just know more about - something shown in the in-app screensaver - there currently does not seem to be a direct way to open that item.

Proposed solution

Pressing right* would close the screensaver and open the detail page of the movie or show currently being displayed. Pressing the back button would bring you back to where you came from. (*or any other key thats on most remotes)

A possible implementation could be:

• add a new user preference for this behavior
• add a checkbox in the existing screensaver settings
• expose the currently displayed LibraryShowcase item from the screensaver ViewModel, for example as currentLibraryShowcaseItemId
• let InAppScreensaver use that ViewModel property when handling the Right key and navigate to the existing item detail page

Maybe something like this could work:

val openItemOnRight = userPreferences[UserPreferences.screensaverOpenItemOnRight]
val itemId = (content as? DreamContent.LibraryShowcase)?.item?.id

if (
	openItemOnRight &&
	itemId != null &&
	event.key == Key.DirectionRight
) {
	...
}

Alternatives considered

Thought of having two actions. One for current item and one for last item, since sometimes the remote has to be grabbed first. But I like the idea, thats this has the chance for a very simple implementation. Especially if it would be just default behaviour without a user prefrence. but then again, it would irritate users that just want to end the screensaver.

Additional information

No response

Other sources

No response

[nielsvanvelzen]

It's actually on the roadmap to open an item from the screensaver. I was thinking of using the play button for that, as most remotes have it and it's not a primary navigation button.
What's important though is that the screensaver contains instructions for it, so a user is aware of the feature, and that it works in both the in-app and system screensaver implementations. We'll also need to verify if Google Play guidelines allow this behavior.

[grunwalski]

Love to hear that! 🤩

Will Google allow it?

I couldn't find anything that would prohibit such a feature, plus DreamService supports interactivity. But after the latest Beta shenaingans, we can only hope for the best.

button choice

[...] I was thinking of using the play button for that, as most remotes have it and it's not a primary navigation button. [...]

I wanted to prevent accidental use of this function. So I was aiming for a button, thats less likely to be pressed when the goal is only: "quit the screensaver, i want to resume playback." (I for one just press play twice in this case.)

btw, my remote doesn’t really have a dedicated play button - it has more of a universal OK button.

UX

What's important though is that the screensaver contains instructions for it, so a user is aware of the feature

What are your thoughts here? Menu item or permanent overlay during the screensaver? Some backgrounds are real works of art. I sometimes wish displaying the logo would be optoinal(*), but I really wouldnt want to have a permanent tool tip on them.

*spontaneous idea: Logo not shown right from the start, but only for the last third(?) of the duration?. Would disturb the image less, esp. when no logo is available and only rendered text is shown. Plus you can quiz yourself on your own library. 😄 #minigame