[Hallmark] Simplify mini-player around Sleep Timer and Play/Pause #96
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Purpose
Make the compact player reflect actual high-frequency use instead of compressing five transport controls into a narrow strip.
Child of the player audit in #47. This issue narrows and supersedes #47's earlier generic compact-player suggestion for the mini-player layout.
Reviewed against current
mainatf9f7feba8e7bb499c6001bf0cc19a38357b7494aon 2026-09-27.User priority
For the mini-player, Sleep Timer is used more often than Back/Forward seeking.
The compact surface should therefore prioritize:
Back/Forward and Stop do not need permanent compact-player buttons.
Proposed compact composition
Primary row:
cover | title + author | sleep | play/pauseProgress and text
Motion
Replace the current
Spring.DampingRatioMediumBouncyentrance with a restrained non-bouncy transition consistent with BookWave's calm glass UI.Reduced-motion behavior must not depend on spatial animation.
Layout and accessibility
Acceptance
Hallmark Slice 1 — design/readiness
Current
mainaudit at8ea2122fc3c1d32bcfc5f0eb295b3521be562ed4:DampingRatioMediumBouncy.Slice change:
cover | title + author | sleep | play/pause.SleepTimerState.remaining; no Compose-owned timer state.Preserved deliberately:
Expected files:
MiniPlayer.ktAccessibility/responsive:
Motion:
Hallmark Slice 1 — implementation staged
Branch:
mcp/hallmark-slice-1-playerBase:
8ea2122fc3c1d32bcfc5f0eb295b3521be562ed4Current HEAD:
f4f90f10a624e310cb87d6abe20482aea444bcb2Implemented for #96:
cover | title + author | sleep | play/pause;SleepTimerState; active countdown uses tabular figures and explicit TalkBack text;Focused mini-player and accessibility tests were updated to protect the reduced control set, expand action, timer semantics and direct Play/Pause behavior.
Verification note: no automated checks, Forgejo Actions or APK workflow were started, per owner instruction. Width/font-scale/device evidence therefore remains pending physical acceptance.