Android: slim the mini player to play/pause, prev/next and favourite; reach the queue from Now Playing only #59

Closed
opened 2026-08-18 05:59:09 +00:00 by logan · 1 comment
Collaborator

Report

While browsing the library, the bottom player only needs play/pause and previous/next (keep the like button). Everything else belongs on the full-screen Now Playing view — including the queue, which should be reachable only from there.

Findings

  • The mini bar currently carries the same control set as desktop plus a queue button, in 424 CSS px.
  • now-playing-view already carries its own queue button, because while it is up index.css hides the bottom bar (body:has(#main-content[data-active-view="now-playing"])). So the "queue from Now Playing" half already exists.
  • Volume goes away entirely on Android (separate issue), which frees more room.

Direction

Phone mini bar = art + title/artist + favourite + prev/play-pause/next, with the larger targets from the control-size issue. Remove the queue button from the phone bar once the queue is a screen. Keep shuffle/repeat on Now Playing.

**Report** While browsing the library, the bottom player only needs play/pause and previous/next (keep the like button). Everything else belongs on the full-screen Now Playing view — including the queue, which should be reachable only from there. **Findings** - The mini bar currently carries the same control set as desktop plus a queue button, in 424 CSS px. - `now-playing-view` already carries its own queue button, because while it is up `index.css` hides the bottom bar (`body:has(#main-content[data-active-view="now-playing"])`). So the "queue from Now Playing" half already exists. - Volume goes away entirely on Android (separate issue), which frees more room. **Direction** Phone mini bar = art + title/artist + favourite + prev/play-pause/next, with the larger targets from the control-size issue. Remove the queue button from the phone bar once the queue is a screen. Keep shuffle/repeat on Now Playing.
logan self-assigned this 2026-08-21 03:08:46 +00:00
logan added
Status
In Progress
and removed
Status
Blocked
1
labels 2026-08-21 03:08:47 +00:00
Author
Collaborator

Taking this together with #56 — argued on #73 first, since it pulls
Phase 3's item 4 forward into item 3's change rather than reordering
anything. Branch: 59-slim-the-mini-player.

Short version: this issue removes controls from the phone's transport
and #56 enlarges what is left, and both are one property on
player-controls, which renders all five buttons unconditionally and is
composed by audio-player and now-playing-view alike. Done
separately the bar is laid out twice and the intermediate state is one
neither issue wants.

This issue's own precondition is now met. #55 merged, so the queue
is a real screen with an entry in the back stack — which is what makes
"remove the queue button from the phone bar" safe rather than a way of
making the queue unreachable. The route is the mini player's art
(.expand, phone only) -> Now Playing -> its own queue button.

Measured on the running app at 424x439 before starting, the phone bar
carries: art, title/artist, favourite, shuffle, prev, play/pause,
next, repeat, queue. The three in bold are what this removes;
shuffle and repeat stay on Now Playing, per the Direction.

The acceptance criterion I am holding to is plan 018's matrix promise —
no action is ever unreachable at any supported size — not the control
count.

Taking this together with #56 — argued on #73 first, since it pulls Phase 3's item 4 forward into item 3's change rather than reordering anything. Branch: `59-slim-the-mini-player`. Short version: this issue removes controls from the phone's transport and #56 enlarges what is left, and both are one property on `player-controls`, which renders all five buttons unconditionally and is composed by `audio-player` and `now-playing-view` alike. Done separately the bar is laid out twice and the intermediate state is one neither issue wants. **This issue's own precondition is now met.** #55 merged, so the queue is a real screen with an entry in the back stack — which is what makes "remove the queue button from the phone bar" safe rather than a way of making the queue unreachable. The route is the mini player's art (`.expand`, phone only) -> Now Playing -> its own queue button. Measured on the running app at 424x439 before starting, the phone bar carries: art, title/artist, favourite, **shuffle**, prev, play/pause, next, **repeat**, **queue**. The three in bold are what this removes; shuffle and repeat stay on Now Playing, per the Direction. The acceptance criterion I am holding to is plan 018's matrix promise — *no action is ever unreachable at any supported size* — not the control count.
logan closed this issue 2026-08-21 04:14:40 +00:00
gitea-actions bot removed the
Status
In Progress
label 2026-08-21 04:14:47 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: yonlu/yellowjacket#59