android: work ribbon segments are not legible and compete with the seek bar
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
Research direction
Start with WorkRibbon.kt in designsystem and WorkRibbonBar.kt in ui/shell/player to see how the ribbon is drawn and placed under the Now Playing artwork. Check the existing screenshot coverage, then capture the listed cases: 4 movements at 25%, 2 movements, and 12 parts. Done when segment gaps and fills make the current movement clear, narrow segments remain visible, and the ribbon reads as secondary to the seek bar while keeping its caption and tap behavior.
Written by the indexing model from the issue text.
Description
The work ribbon under the Now Playing artwork is not legible as a segmented progress indicator. A reviewer did not notice it had segments, read the small fill dot at the start of an upcoming segment as a rendering mistake, and then found two progress bars (one non-interactive) confusing.
Where: WorkRibbon.kt (designsystem) and WorkRibbonBar.kt (ui/shell/player). Caption "II of IV · 26:08 left in work" and the tap-to-list-movements behaviour were liked and stay.
Expected: the ribbon reads at a glance as "movements of this work, you are in this one", and as clearly secondary to the seek bar.
- Segments separated by a visible gap (proportional widths kept); played segments filled, the current one filled to its position, upcoming segments outline or low-alpha track only, no partial fill or dot in any segment that is not current.
- Thinner and lower-contrast than the seek bar, closer to the caption than to the seek bar, so the two never read as a pair. No thumb.
- Keep it non-interactive for seeking; tap opens the movement list as today.
- Do not merge it with the seek bar: the seek bar scrubs one file, the ribbon spans several; a merged bar would change tracks mid-drag.
Screenshot test: 4-movement work in movement II at 25%; 2-movement work; a 12-part work (narrow segments must not collapse into a dotted line).
Impact U2 (a reviewer misread the feature as a bug) · Reach R2 (every classical Now Playing) · Implemented: partly (ribbon exists, segments too subtle) · Design fit: fits · Complexity: S
- Dominant language
- Kotlin
- Stars
- 232
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from timusus/Shuttle2
-
enhancement impact:U2 P3 reach:R1 size:S
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
design
-
design
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 52/100
All issues in timusus/Shuttle2
Similar issues
-
Messages: Subscribe to the new communication websocket topicsPossibly taken @krusche claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ls1intum/artemis-android#801 ·
Maintainers usually reply within 1 day
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
keiyoushi/extensions-source#20362 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
enhancement good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
software-mansion/enriched-markdown#1084 ·
Maintainers usually reply within 2 days