(2021-10-01, 02:51)amasephy Wrote:
Thanks for offering your support, this will help once I enabled the "swipe left" in the remote screen. This will need some time, but I will announce it here, once the software is available via TestFllight.
The NowPlaying-bound remote screen supports a whole different way of using the remote, like I do. I am not using the TV at all and have a headless Kodi setup, for Music playback only. In such setup you typically use the App to browse the content and start playing it from the database browser. The App then switches to NowPlaying automatically to reflect what is playing and allow the basic controls (play, pause, seek, ...). The remote screen with the volume control is just one click away from there.
Your suggestion to enlarge the play/pause/seek buttons is noted. What can be done w/o too much hassle is to rebalance the height of the first, second and last row of buttons -- allowing the play/pause/seek buttons more size and reducing the others a bit. Definitely the layout can be further optimized, we just need to figure out what's best from a user point of view. E.g. several users asked for the possibility to move the remote to the bottom as it was difficult to reach the navigation button on large iPhone when using the App one-handed. What I had in mind was to either add more "main menu" buttons (e.g. to access Favourites, TV, Radio, ...). This could be done with adding another row of buttons -- only on bigger screens --, or simply support longpress. In fact, the longpress is implemented from some of the buttons, but it does not work for my Kodi 19 test server. I am not sure, if this functionality broke with a past Kodi server update.
Both solutions have pros and cons:
- New buttons Pro: Clear UI, you get what you see. More effort to implement as the layout needs to be reworked.
- New buttons Con: Needs space and cannot be done for smaller devices, which results in inconsistency over different devices. Navigate buttons would again be located higher on the screen, which impacts the one-handed usability.
- Longpress Pro: No additional space needed. Easier to implement, few layout changes.
- Longpress Con: Need to find a way to visualize the longpress function, which will impact the button design and might be hard to read (e.g. having two icons per button).