[Hallmark] Refine Book screen into a responsive reader-first detail page #100

Open
opened 2026-09-27 14:35:30 +02:00 by alexander · 0 comments
Owner

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 main at f9f7feba8e7bb499c6001bf0cc19a38357b7494a on 2026-09-27.

What to preserve

The current Book screen already has several good decisions:

  • flatter editorial presentation rather than glass-card repetition;
  • cover artwork with physical depth;
  • left-aligned title/author/series hierarchy;
  • expandable synopsis;
  • separate reader-facing content and technical More info;
  • adaptive two-pane layout on wider windows;
  • mini-player clearance on the phone layout;
  • linked authors/series and accessible Material controls.

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:

  • fixed 140dp cover;
  • 16dp inter-column spacing;
  • right column begins with Download + Play + More icon buttons;
  • title/author/series follow beneath those controls.

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 / series

Then below the identity block:

[ Download ] [ Resume / Play ]

  • Play/Resume should be the strongest action and should be labelled, not merely one of three equal icon buttons.
  • Keep truthful loading/resume behavior from the existing player action.
  • Download remains direct when permitted.
  • Move the overflow entry out of the constrained hero action row, preferably into the top bar.
  • At narrow widths / large text, reduce cover size before crushing metadata; if necessary, allow a stacked hero.
  • Treat roughly 112–120dp as a prototype range for narrow layouts, not a hard requirement.
  • Preserve the 140dp-style presence where width allows.

2. Avoid simultaneous duplicate title presentation

The current TopAppBar shows the full book title while the hero prints the title again.

Preferred behavior:

  • while the hero title is visible, top chrome primarily carries Back + More;
  • once the hero title scrolls away, the book title may appear in the app bar.

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:

  • total duration + local/download availability;
  • listened time;
  • remaining time;
  • percentage where useful;
  • restrained progress bar.

Example information hierarchy, not required wording:

12h 42m · Downloaded

8h 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

  • History
  • Mark finished / unfinished
  • Discard progress

Offline

  • Manage downloads
  • Delete local copy

Library management

  • Edit metadata
  • Open web client
  • Embed metadata
  • Remove from server

Information

  • More info

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:

  • what book is this?
  • who wrote/narrated it?
  • where is it in the series?
  • where am I in it?
  • what is it about?
  • what kind of book is it?

Keep concise publication context where useful, e.g.:

  • year;
  • publisher;
  • language.

Move low-frequency technical metadata into More info:

  • ISBN;
  • ASIN;
  • server item ID;
  • track count;
  • raw file/storage facts where appropriate.

Do not remove technical metadata; change its hierarchy.

6. Clarify Genres versus Tags

Current BookLabels merges genres + tags into identical read-only chips.

During implementation, inspect real library data and choose one of:

  • distinct Genres and Tags sections when both are meaningful to readers; or
  • show Genres on the reader-facing page and move operational/housekeeping Tags to More info.

Do not silently treat server tags as genres.

Responsive and accessibility acceptance

Validate:

  • 320 / 375 / 414 / 768dp widths;
  • portrait, landscape and wide/two-pane layouts;
  • font scales 1.0 / 1.3 / 2.0;
  • long title/subtitle, multiple authors, narrator list and multiple series memberships;
  • missing artwork;
  • unstarted / in-progress / finished books;
  • download none / active / failed / complete;
  • light, dark, AMOLED and background packs;
  • TalkBack order and independent action semantics;
  • reduced motion;
  • mini-player clearance.

The action hierarchy must remain understandable without relying on color alone.

Implementation starting points

  • app/src/main/kotlin/com/example/shelfplayer/feature/book/BookScreen.kt
    • BookScreen
    • BookDetails
    • ActionPane
    • FactStrip
    • BookHeader
    • ProgressSummary
    • BookLabels
    • PublicationFacts
  • app/src/main/kotlin/com/example/shelfplayer/feature/book/BookOverflowMenu.kt
  • app/src/main/kotlin/com/example/shelfplayer/feature/book/DownloadButton.kt

Use the existing architecture and state owners. This issue authorizes presentation/information-hierarchy changes, not a playback/download/domain rewrite.

## 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 `main` at `f9f7feba8e7bb499c6001bf0cc19a38357b7494a` on 2026-09-27. ## What to preserve The current Book screen already has several good decisions: - flatter editorial presentation rather than glass-card repetition; - cover artwork with physical depth; - left-aligned title/author/series hierarchy; - expandable synopsis; - separate reader-facing content and technical More info; - adaptive two-pane layout on wider windows; - mini-player clearance on the phone layout; - linked authors/series and accessible Material controls. 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: - fixed 140dp cover; - 16dp inter-column spacing; - right column begins with Download + Play + More icon buttons; - title/author/series follow beneath those controls. 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 / series` Then below the identity block: `[ Download ] [ Resume / Play ]` - Play/Resume should be the strongest action and should be labelled, not merely one of three equal icon buttons. - Keep truthful loading/resume behavior from the existing player action. - Download remains direct when permitted. - Move the overflow entry out of the constrained hero action row, preferably into the top bar. - At narrow widths / large text, reduce cover size before crushing metadata; if necessary, allow a stacked hero. - Treat roughly 112–120dp as a prototype range for narrow layouts, not a hard requirement. - Preserve the 140dp-style presence where width allows. ## 2. Avoid simultaneous duplicate title presentation The current TopAppBar shows the full book title while the hero prints the title again. Preferred behavior: - while the hero title is visible, top chrome primarily carries Back + More; - once the hero title scrolls away, the book title may appear in the app bar. 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: - total duration + local/download availability; - listened time; - remaining time; - percentage where useful; - restrained progress bar. Example information hierarchy, not required wording: `12h 42m · Downloaded` `8h 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 - History - Mark finished / unfinished - Discard progress ### Offline - Manage downloads - Delete local copy ### Library management - Edit metadata - Open web client - Embed metadata - Remove from server ### Information - More info 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: - what book is this? - who wrote/narrated it? - where is it in the series? - where am I in it? - what is it about? - what kind of book is it? Keep concise publication context where useful, e.g.: - year; - publisher; - language. Move low-frequency technical metadata into More info: - ISBN; - ASIN; - server item ID; - track count; - raw file/storage facts where appropriate. Do not remove technical metadata; change its hierarchy. ## 6. Clarify Genres versus Tags Current `BookLabels` merges `genres + tags` into identical read-only chips. During implementation, inspect real library data and choose one of: - distinct **Genres** and **Tags** sections when both are meaningful to readers; or - show Genres on the reader-facing page and move operational/housekeeping Tags to More info. Do not silently treat server tags as genres. ## Responsive and accessibility acceptance Validate: - 320 / 375 / 414 / 768dp widths; - portrait, landscape and wide/two-pane layouts; - font scales 1.0 / 1.3 / 2.0; - long title/subtitle, multiple authors, narrator list and multiple series memberships; - missing artwork; - unstarted / in-progress / finished books; - download none / active / failed / complete; - light, dark, AMOLED and background packs; - TalkBack order and independent action semantics; - reduced motion; - mini-player clearance. The action hierarchy must remain understandable without relying on color alone. ## Implementation starting points - `app/src/main/kotlin/com/example/shelfplayer/feature/book/BookScreen.kt` - `BookScreen` - `BookDetails` - `ActionPane` - `FactStrip` - `BookHeader` - `ProgressSummary` - `BookLabels` - `PublicationFacts` - `app/src/main/kotlin/com/example/shelfplayer/feature/book/BookOverflowMenu.kt` - `app/src/main/kotlin/com/example/shelfplayer/feature/book/DownloadButton.kt` Use the existing architecture and state owners. This issue authorizes presentation/information-hierarchy changes, not a playback/download/domain rewrite.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
alexander/Audiobookshelf-Manager-Claude#100
No description provided.