-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android TV/button navigation needs a rethink/redesign #11197
Labels
Android TV
Issue is related to Android TV
feature request
Issue is related to a feature in the app
GUI
Issue is related to the graphical user interface
Comments
opusforlife2
added
feature request
Issue is related to a feature in the app
GUI
Issue is related to the graphical user interface
Android TV
Issue is related to Android TV
labels
Jun 21, 2024
This was referenced Jun 21, 2024
opusforlife2
changed the title
Android TV navigation needs a rethink/redesign
Android TV/button navigation needs a rethink/redesign
Jun 21, 2024
This was referenced Jun 21, 2024
Please, also add #11194 |
🤦 That tab was the first one I opened and somehow forgot to deal with it. |
6 tasks
From user's perspective, I've been using yuliskov/SmartTube on my Android TV (CCWGTV) and I tried it for fun on a tablet, and can see that it's basically unusable with touch controls. But might be a good inspiration for the TV controller navigation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Android TV
Issue is related to Android TV
feature request
Issue is related to a feature in the app
GUI
Issue is related to the graphical user interface
Checklist
Feature description
Newpipe should be completely navigable and accessible using Android TV or similar devices. There should be no touchscreen-exclusive actions.
Why do you want this feature?
Plenty of issues opened about TV navigation being problematic. I'm closing them all in favour of a single, easier-to-track issue. This will have to be done during/post rewrite anyway.
Additional information
No response
The text was updated successfully, but these errors were encountered: