-
-
Notifications
You must be signed in to change notification settings - Fork 186
A few features I'd like to see get added #572
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
Comments
|
So, my suggestion in order to make it consistent across both the yt and non-yt style miniplayers, would be to slot it inside the queue box (not sure how to call it, I mean when you open the queue) as both miniplayers style share that point in common. There you could put it at the top or bottom as you see fit. The bottom is the same for both players when you open the queue, so maybe there, and there is some space too. See the attached pic at the end of this please.
Thanks for listening to my ideas! |
Hi, I tried the beta: If I may voice a concern regarding the landscape layout, it is that the player side occupies a relatively small space compared to the section reserved for browsing the app. If I was to have a say, I would make the player occupy the whole space, as users can always get out of the player if they want to access the settings and other sections of the app. If at least the area occupied by the player could be user-scalable, that would be great, but ideally the whole of it would be for the player and users could use the back button or swipe downwards on the player to access other stuff. A constraint of the player being so small is that the queue is really hard to read and navigating that area becomes difficult as well. Also having the player take the whole space, on top of making it easier to use would also look cooler easthetically speaking. The queue could remain visible at all times, maybe to the right side of the player for example, or brought up just when needed with a sideways or upwards swipe, idk. However this is a promising first step, here's hoping to see it evolve. Thanks. |
Uh oh!
There was an error while loading. Please reload this page.
Auto-rotate. Whether using youtube-style or non youtube-style miniplayer, this feature would be great. When using youtube-syle miniplayer the video could automatically switch to full screen when rotating the phone landscape -wise, and when using non youtube-style miniplayer we could see the current playlist/queue on the side.
Being able to swap between youtube-style miniplayer or non youtube-style miniplayer on the fly, that is in the player itself without having to access the menu.
When using picture-in-picture mode,
it would be great to show controls (pause, rewind, forward) available in the video for a short time then disappear, when clicking on it. Currently one has to go into the player again or use the notification bar to use controls when using pip.Edit: Now I see controls are there on pip, not sure why I didn't see it before. But still, we have previous/next as well as play/pause, but rewind/forward could be useful too (as an option instead of previous/next)The seekbar inside videos shows how many minutes forwards or backwards we are moving, instead of the time point to which one would want to move. Having the latter would be better imo as users often remember a point in a video they want to go to and instead of having to do the math to add or substract how any minutes more or less they need to move in a video, they could just scroll the bar and go directly to that point if it showed that instead of increments of minutes being changed.
Overall these few things would help make using the app more immersive while cutting the number of steps required to do so.
Apps
See Outertune for non youtube-style miniplayer. The player automatically switches to landscape or portrait mode depending on the orientation of the phone. How the layout is then customized is up to you the dev.
For youtube-style mini player, obviously the Yt app, or Newpipe, would be good examples.
Thank you.
The text was updated successfully, but these errors were encountered: