[Hallmark] Give Continue listening a clear leading Resume card #49

Open
opened 2026-09-18 13:55:01 +02:00 by alexander · 0 comments
Owner

Problem and outcome

Home currently renders Continue listening through the same compact 160 dp shelf-card pattern used for discovery. Resuming the current audiobook deserves a clearer priority than browsing many equal choices.

Introduce a wider leading Continue listening card that makes the book, progress and Resume action immediately readable. Retain compact access to other in-progress books. Child of #48; source-based design proposal, pending rendered validation. Primary owner: UI & Experience.

Proposed composition

  • Keep the existing Continue listening section heading.
  • One leading card spans the available content column, with a bounded cover on the left and a flexible text/action column on the right when space permits.
  • Preserve the established author-before-title ordering, but give the title stronger type weight/size. Permit natural title wrapping rather than an always-running marquee.
  • Show one primary progress fact, preferably time remaining, with a restrained progress indicator. Include chapter name or chapter time only when trustworthy data is already available; do not fetch or fabricate metadata to fill a slot.
  • Give Resume a labelled, generous tap target distinct from opening book details. If this is the actively playing item, use Pause and the actual playback state. If playback is paused, Resume delegates to the existing player action.
  • Show truthful offline/download status only where available; cached metadata alone must not imply offline playability.
  • Other in-progress titles remain a compact horizontal shelf below, excluding the leading item. Omit that shelf when no other items exist.
  • Keep the leading card compact enough that browsing content remains discoverable below it. Avoid a giant promotional hero, decorative badges, animated gradients or unnecessary shadows.

Which book leads

Use the existing active-profile playback/remembered-book and resume-freshness owners. Presentation must not introduce a new remembered-book store, choose the furthest progress as truth, or overwrite remembered identity from remote recency.

During implementation, verify the current supported contract for the leading item: resolve the existing profile-visible remembered/loaded book if appropriate, otherwise use the existing Continue shelf ordering. If these concepts are not exposed together, make the presentation mapping explicit with the existing owner before changing behavior. Never expose an inaccessible book or let a stale previous-profile result flash.

The card must not seek or auto-start merely because Home appears or its contents refresh. Resume follows the same policy as existing playback surfaces.

Responsive and state behavior

  • On narrow widths or large text, reduce cover size or stack the content; text and control targets win over artwork. No fixed total height.
  • On tablets, cap the reading width rather than stretching the card across the entire window.
  • Missing/failed artwork gets the existing stable fallback.
  • While resolving the leading item, preserve stable structure without briefly claiming there is no listening history.
  • If no eligible Continue item exists, omit the section and allow existing discovery/recent content to lead.
  • A playback request shows localized pending/error state without blanking cached content. Errors must explain a useful next action through existing application error handling.
  • Preserve mini-player clearance and existing navigation/scroll state.
  • Keep both details and transport independently accessible to TalkBack; announce title and labelled progress once, not duplicated cover text.

Implementation starting points

Audit snapshot: main 8f0ff59266.

  • app/src/main/kotlin/com/example/shelfplayer/feature/home/HomeShelvesUi.kt:58–159 (Continue shelf and shared book card composition)
  • app/src/main/kotlin/com/example/shelfplayer/feature/home/HomeScreen.kt:1180–1186 (shelf integration)
  • Existing player callbacks and profile-scoped remembered-book/resume owners; re-read current main before implementation.

Preserve Compose/Material 3, semantic colors, existing component ownership and optional appearance choices. No backend, download, synchronization or playback-policy redesign.

Acceptance

  • The leading book and Resume/Pause action are apparent at a glance without waiting for scrolling text.
  • Other Continue items remain discoverable and there is no duplicate leading card.
  • Correct state for active, paused, first-start/unavailable metadata, offline, failed artwork, loading/error and no eligible book.
  • Profile switch never exposes stale identity; pressing Resume reaches existing playback policy and never an independent progress algorithm.
  • Render at 320/375/414/768 dp, portrait/landscape and font scales 1.0/1.3/2.0, using long titles/authors and long-duration books.
  • Check light/dark/AMOLED/background packs, contrast, reduced motion and at least 48 dp interactive targets.
  • Compare actual screenshots with the current Home; verify TalkBack traversal and separate details/transport taps.
  • Run applicable repository checks and focused UI tests, with device evidence for actual rendering. Perform Hallmark's final hierarchy/restraint/state review.
  • Respect docs/roadmap.md sequencing. This issue does not authorize deletion, a navigation rebuild or an automatic playback behavior change.
<!-- Hallmark · pre-emit critique: P5 H5 E4 S5 R5 V4 --> ## Problem and outcome Home currently renders Continue listening through the same compact 160 dp shelf-card pattern used for discovery. Resuming the current audiobook deserves a clearer priority than browsing many equal choices. Introduce a wider leading Continue listening card that makes the book, progress and Resume action immediately readable. Retain compact access to other in-progress books. Child of #48; source-based design proposal, pending rendered validation. Primary owner: UI & Experience. ## Proposed composition - Keep the existing Continue listening section heading. - One leading card spans the available content column, with a bounded cover on the left and a flexible text/action column on the right when space permits. - Preserve the established author-before-title ordering, but give the title stronger type weight/size. Permit natural title wrapping rather than an always-running marquee. - Show one primary progress fact, preferably time remaining, with a restrained progress indicator. Include chapter name or chapter time only when trustworthy data is already available; do not fetch or fabricate metadata to fill a slot. - Give Resume a labelled, generous tap target distinct from opening book details. If this is the actively playing item, use Pause and the actual playback state. If playback is paused, Resume delegates to the existing player action. - Show truthful offline/download status only where available; cached metadata alone must not imply offline playability. - Other in-progress titles remain a compact horizontal shelf below, excluding the leading item. Omit that shelf when no other items exist. - Keep the leading card compact enough that browsing content remains discoverable below it. Avoid a giant promotional hero, decorative badges, animated gradients or unnecessary shadows. ## Which book leads Use the existing active-profile playback/remembered-book and resume-freshness owners. Presentation must not introduce a new remembered-book store, choose the furthest progress as truth, or overwrite remembered identity from remote recency. During implementation, verify the current supported contract for the leading item: resolve the existing profile-visible remembered/loaded book if appropriate, otherwise use the existing Continue shelf ordering. If these concepts are not exposed together, make the presentation mapping explicit with the existing owner before changing behavior. Never expose an inaccessible book or let a stale previous-profile result flash. The card must not seek or auto-start merely because Home appears or its contents refresh. Resume follows the same policy as existing playback surfaces. ## Responsive and state behavior - On narrow widths or large text, reduce cover size or stack the content; text and control targets win over artwork. No fixed total height. - On tablets, cap the reading width rather than stretching the card across the entire window. - Missing/failed artwork gets the existing stable fallback. - While resolving the leading item, preserve stable structure without briefly claiming there is no listening history. - If no eligible Continue item exists, omit the section and allow existing discovery/recent content to lead. - A playback request shows localized pending/error state without blanking cached content. Errors must explain a useful next action through existing application error handling. - Preserve mini-player clearance and existing navigation/scroll state. - Keep both details and transport independently accessible to TalkBack; announce title and labelled progress once, not duplicated cover text. ## Implementation starting points Audit snapshot: main 8f0ff5926687b3373703ee972dbb1392a0792d63. - app/src/main/kotlin/com/example/shelfplayer/feature/home/HomeShelvesUi.kt:58–159 (Continue shelf and shared book card composition) - app/src/main/kotlin/com/example/shelfplayer/feature/home/HomeScreen.kt:1180–1186 (shelf integration) - Existing player callbacks and profile-scoped remembered-book/resume owners; re-read current main before implementation. Preserve Compose/Material 3, semantic colors, existing component ownership and optional appearance choices. No backend, download, synchronization or playback-policy redesign. ## Acceptance - The leading book and Resume/Pause action are apparent at a glance without waiting for scrolling text. - Other Continue items remain discoverable and there is no duplicate leading card. - Correct state for active, paused, first-start/unavailable metadata, offline, failed artwork, loading/error and no eligible book. - Profile switch never exposes stale identity; pressing Resume reaches existing playback policy and never an independent progress algorithm. - Render at 320/375/414/768 dp, portrait/landscape and font scales 1.0/1.3/2.0, using long titles/authors and long-duration books. - Check light/dark/AMOLED/background packs, contrast, reduced motion and at least 48 dp interactive targets. - Compare actual screenshots with the current Home; verify TalkBack traversal and separate details/transport taps. - Run applicable repository checks and focused UI tests, with device evidence for actual rendering. Perform Hallmark's final hierarchy/restraint/state review. - Respect docs/roadmap.md sequencing. This issue does not authorize deletion, a navigation rebuild or an automatic playback behavior change.
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#49
No description provided.