View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0019663 | MMA | Navigation | public | 2022-12-22 19:59 | 2024-06-27 16:02 |
Reporter | rusty | Assigned To | |||
Priority | urgent | Severity | minor | Reproducibility | always |
Status | feedback | Resolution | open | ||
Product Version | 2.0.0 | ||||
Target Version | 2.0.2 | ||||
Summary | 0019663: Landscape view: little space is available to browse/view content | ||||
Description | On phone devices, when the user rotates to landscape mode, there's almost no space available to view content because only about 1/3 of the view is available to display content: - hamburger menu / breadcrumb / Search bar take up one row - Tab navigation bar takes up another row - MiniPlayer takes up another row The remaining ~1/3 of the view isn't even enough to display an album in Grid view, and what can be displayed is partially obscured by the status bar! Possible solutions would be: 1) Hide portions of the view when scrolling. i.e. a) Collapse the first two rows when the user scrolls down / uncollapse when scrolling back up b) Hide the status indicator once the user scrolls away from the top of the view 2) 'split' the view in a manner similar to the Playing view. e.g. On the left (2/3): - Hamburger menu & Tab navigation - Content On the right (1/3) - View switcher & Search - Miniplayer (would require an alternate layout) The first solution seems simpler and better. Moreover it can be applied to the regular layout as well to provide more space for content. | ||||
Tags | No tags attached. | ||||
Fixed in build | |||||
|
Another example on Android TV UI. |
|
Here's an example of what I meant. The issue is actually quite severe as it makes browsing in landscape mode near-impossible, and it's particularly bad problematic when it comes to video since video is normally watched in landscape mode. |
|
Both solutions sound interesting and can be combined. However, both solutions are time-consuming to debug, affect stability, and are prone to regression. So I definitely prefer to postpone it to 2.0.1. |