View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0020093 | MMA | Android Auto | public | 2023-06-13 10:28 | 2023-06-22 19:50 |
| Reporter | martin | Assigned To | |||
| Priority | high | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Platform | Android | OS | - | OS Version | all |
| Product Version | 2.0.0 | ||||
| Target Version | 2.0.1 | ||||
| Summary | 0020093: Add "Browse tracks" to album views (Android Auto) | ||||
| Description | Adding "Browse tracks" will be especially useful for audiobooks and podcasts. However, these lists should be either limited or split(due to AA browsing issues), e.g. 1-100 100-200 Albums usually don't contain a large number of tracks, so we can 1) have a fixed batch size, e.g. 100 OR 2) Use the existing option "Limit list size for external apps", but increase the default value from 0 to non-zero value. The value used as a batch size. Tracks will be displayed only under new "Browse tracks" item. All end nodes should contain: "Play All" "Play All(random play)" "Browse tracks" and for audiobooks and podcasts "Continue" (only if a track is bookmarked). "Play All" "Browse Tracks" | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Just few additions: I'd suggest to tweak wording for Music: 1. Play 2. Shuffle 3. Browse And for audiobooks/podcasts: 1. Continue 2. Play 3. Browse Note that for large folders (i.e. audiobooks, albums, etc.) the Browse would be like "Browse (1-20)", "Browse (21-40)", etc. In the chat I forgot to discuss Artists. They also kind of miss Browse action in order to list individual albums by given artist. There could be both "Browse Albums" and "Browse Tracks", but since AA should be kept as simple as possible, I guess that a single "Browse" item to list Albums would be better? |
|
|
So if I'm understanding correctly, tapping Podcasts ---> Podcast A 22 tracks Podcast B 5 tracks Podcast C 17 tracks And then tapping Podcast B ---> Continue Play all (rather than Play) Browse And if the user taps Browse ---> Track 1 Track 2 Track 3 Track 4 Track 5 .... And the list would be positioned at the current track, and there would be an indicator showing which tracks have played / partially played (and presumably, the same approach would be used for Audiobooks)? And anytime the list > Maximum list size, it would be divided into chunks of the maximum list size? ------------------------------------------------------------------------------------------------------------------------- As to taking the above approach (Play all, Play all (shuffled), Browse) for Artists and other nodes such as playlists etc., I would just open tracks directly in all cases. But I thin that this is a lower priority item that can be treated separately if it's non-trivial. |
|
|
Note that all the proposals have to take into account couple of limitations (i.e. we can't implement just whatever we'd like to): L1. We can't show just anything, only a line of text. L2. We can't position the list. Each item can only do one of two things: either play an item or open a sub-list, that's it. L3. We can't show unlimited # of items, as it results in freeze of the UI (depending of AA implementation) That said, I agree with the idea to skip Browse button when there's only a few items in the list (which typically is the case for music albums). I.e.: Album: Play all Shuffle Track 1 Track 2 ... (and replace the items by Browse button when there's more than X tracks) Artist: Play all Shuffle Browse Albums (opens a list of albums by the artist) Tracks A-G (just an example, the exact categories would depend on the # of tracks by the Artist) Tracks H-R Tracks S-Z Playlist: Play all Shuffle Tracks #1-20 (for very short playlist, all tracks could be listed here, without the need for sub-lists) Tracks 0000021-40 As for the bookmark/progress indicator for AB and Podcasts, we could show it e.g. as [100%] for completed tracks, [56%] for tracks in progress and either [0%] or just nothing for unlistened tracks. |
|
|
I agree, but subgroups must be formed according to the total number of tracks. This should not be done until the user actually wants to browse the tracks. Therefore, I suggest: Album: ------------------------ Play all Play all(Shuffle) Browse tracks Tracks ------------------------ Tracks 1..200; Tracks 200..400; The number of tracks displayed at once doesn't have to be that small. Artist: Play all Play all(Shuffle) Browse Albums Browse tracks I consider this solution to be more consistent and easier to implement. |
|
|
Note: as described at 0020110:0072317, the Genres node doesn't conform to the approach described at 0020093:0072223. When we implement this, it should be implemented for the Genres node as well. |
