[Hallmark] Refine Book screen into a responsive reader-first detail page #100
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
Refine the Book screen into a calm, reader-oriented detail page while preserving the strong parts of its current architecture.
This is a focused Hallmark design issue. It does not replace the existing playback, download, metadata or history ownership.
Reviewed against current
mainatf9f7feba8e7bb499c6001bf0cc19a38357b7494aon 2026-09-27.What to preserve
The current Book screen already has several good decisions:
Do not turn this into another Home-style card grid or a glass container stack.
1. Fix the responsive hero/action layout
Current phone hero:
At 320dp width, after 16dp outer margins and the 140dp cover, only about 132dp remains for the right column. Three 48dp controls plus spacing need materially more than that before title text is considered.
Proposed direction
Make the book identity lead, controls follow.
Preferred hero hierarchy:
cover | title / subtitle / author / narrator / seriesThen below the identity block:
[ Download ] [ Resume / Play ]2. Avoid simultaneous duplicate title presentation
The current TopAppBar shows the full book title while the hero prints the title again.
Preferred behavior:
A simpler first implementation may use a contextual app-bar title while leaving the actual title in the hero, but avoid two equally visible copies of the same long title.
Do not introduce complex collapse motion merely for spectacle; the transition must remain restrained and reduced-motion safe.
3. Make progress answer the audiobook question
Current reader-facing facts include duration + track count + local availability, followed by a percentage/progress bar.
Prefer listener-facing progress such as:
Example information hierarchy, not required wording:
12h 42m · Downloaded8h 02m listened · 4h 40m left · 63%Track count is technical file structure and should move to More info unless a real user workflow requires it on the primary page.
Use tabular figures for time/progress values.
4. Organize the overflow surface
The current overflow can contain History, mark Finished/Unfinished, Discard progress, Local files, Delete local, Edit metadata, Web client, Embed metadata, Remove from server and More info.
The actions are individually valid, but the flat dropdown becomes a large mixed-purpose list.
On phones, prototype a grouped secondary surface, preferably a bottom sheet:
Listening
Offline
Library management
Information
On larger windows a popup/menu may remain appropriate.
Preserve permissions, confirmation behavior and destructive-action wording. Do not expose unavailable administrator actions merely to keep groups symmetrical.
History on this Book screen remains intentionally read-only unless a separate product decision changes that behavior. The full player issue #97 owns History-first playback navigation.
5. Keep the main page reader-oriented
Primary page should answer:
Keep concise publication context where useful, e.g.:
Move low-frequency technical metadata into More info:
Do not remove technical metadata; change its hierarchy.
6. Clarify Genres versus Tags
Current
BookLabelsmergesgenres + tagsinto identical read-only chips.During implementation, inspect real library data and choose one of:
Do not silently treat server tags as genres.
Responsive and accessibility acceptance
Validate:
The action hierarchy must remain understandable without relying on color alone.
Implementation starting points
app/src/main/kotlin/com/example/shelfplayer/feature/book/BookScreen.ktBookScreenBookDetailsActionPaneFactStripBookHeaderProgressSummaryBookLabelsPublicationFactsapp/src/main/kotlin/com/example/shelfplayer/feature/book/BookOverflowMenu.ktapp/src/main/kotlin/com/example/shelfplayer/feature/book/DownloadButton.ktUse the existing architecture and state owners. This issue authorizes presentation/information-hierarchy changes, not a playback/download/domain rewrite.