[Polish] Evaluate shared book-cover transition into Book details #104

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

Purpose

Evaluate one deliberately limited shared-element transition for BookWave: the book cover moving from a library/list context into the Book detail screen and back.

This is a later polish item, not a prerequisite for the navigation/motion cleanup. Implement only after the relevant Home/list/Book layouts have stabilized (#49, #50, #95, #100).

Reviewed against current main at f9f7feba8e7bb499c6001bf0cc19a38357b7494a on 2026-09-27.

Why this element

The book cover is one of the few visual elements whose identity genuinely persists across:

  • Home shelf card → Book;
  • flat Books list → Book;
  • Series book row/card → Book;
  • Author book row → Book.

A cover transition can therefore explain continuity rather than decorate navigation.

Do not generalize this into shared-element animation for titles, buttons, glass cards, entire rows or every destination.

Proposed behavior to prototype

Forward:

  • tapped cover remains visually identifiable as it settles into the Book hero;
  • surrounding destination uses the app's normal shallow detail transition;
  • transition must not delay destination usability.

Back:

  • where the originating item still exists and is laid out, cover returns toward its source;
  • if the origin is unavailable/off-screen/changed, fall back cleanly to the normal Back transition;
  • never jump-scroll a list merely to manufacture the reverse animation.

Required contexts

Prototype first on one stable path, preferably flat list → Book after #50/#100.

Only expand to shelves/Series/Author if the implementation stays simple and robust.

Predictive Back

If the chosen Navigation Compose shared-transition API supports predictive Back cleanly in the project's current versions, verify the cover transformation tracks Back gesture progress.

Do not build a bespoke gesture engine solely for this polish.

Image/state rules

  • Missing/error cover uses the stable placeholder without geometry jump.
  • Artwork completing its load mid-transition must not resize the shared bounds unexpectedly.
  • Finished/active/download state chrome should not become part of the shared element unless proven necessary.
  • Preserve cover aspect ratio.
  • Do not expose stale cover art from a previous profile/library during navigation.

Accessibility / reduced motion

  • Shared movement must not duplicate semantic nodes.
  • Reduced/disabled motion falls back to the standard route transition.
  • Destination focus should land according to screen semantics, not remain trapped on an image.

Acceptance

  • The cover transition clarifies “this is the same book” and does not add motion elsewhere.
  • Back has a robust fallback when the source item cannot participate.
  • No forced list scroll or stale-profile flash.
  • Works with loaded/missing/failed artwork, narrow/large text, light/dark/AMOLED/background packs.
  • Performance remains smooth on representative hardware.
  • Compare the prototype against the standard route transition and keep it only if it materially improves continuity.

This issue is explicitly optional polish. The app must feel coherent without it.

## Purpose Evaluate one deliberately limited shared-element transition for BookWave: the **book cover** moving from a library/list context into the Book detail screen and back. This is a later polish item, not a prerequisite for the navigation/motion cleanup. Implement only after the relevant Home/list/Book layouts have stabilized (#49, #50, #95, #100). Reviewed against current `main` at `f9f7feba8e7bb499c6001bf0cc19a38357b7494a` on 2026-09-27. ## Why this element The book cover is one of the few visual elements whose identity genuinely persists across: - Home shelf card → Book; - flat Books list → Book; - Series book row/card → Book; - Author book row → Book. A cover transition can therefore explain continuity rather than decorate navigation. Do **not** generalize this into shared-element animation for titles, buttons, glass cards, entire rows or every destination. ## Proposed behavior to prototype Forward: - tapped cover remains visually identifiable as it settles into the Book hero; - surrounding destination uses the app's normal shallow detail transition; - transition must not delay destination usability. Back: - where the originating item still exists and is laid out, cover returns toward its source; - if the origin is unavailable/off-screen/changed, fall back cleanly to the normal Back transition; - never jump-scroll a list merely to manufacture the reverse animation. ## Required contexts Prototype first on one stable path, preferably flat list → Book after #50/#100. Only expand to shelves/Series/Author if the implementation stays simple and robust. ## Predictive Back If the chosen Navigation Compose shared-transition API supports predictive Back cleanly in the project's current versions, verify the cover transformation tracks Back gesture progress. Do not build a bespoke gesture engine solely for this polish. ## Image/state rules - Missing/error cover uses the stable placeholder without geometry jump. - Artwork completing its load mid-transition must not resize the shared bounds unexpectedly. - Finished/active/download state chrome should not become part of the shared element unless proven necessary. - Preserve cover aspect ratio. - Do not expose stale cover art from a previous profile/library during navigation. ## Accessibility / reduced motion - Shared movement must not duplicate semantic nodes. - Reduced/disabled motion falls back to the standard route transition. - Destination focus should land according to screen semantics, not remain trapped on an image. ## Acceptance - The cover transition clarifies “this is the same book” and does not add motion elsewhere. - Back has a robust fallback when the source item cannot participate. - No forced list scroll or stale-profile flash. - Works with loaded/missing/failed artwork, narrow/large text, light/dark/AMOLED/background packs. - Performance remains smooth on representative hardware. - Compare the prototype against the standard route transition and keep it only if it materially improves continuity. This issue is explicitly **optional polish**. The app must feel coherent without it.
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#104
No description provided.