[Polish] Evaluate shared book-cover transition into Book details #104
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
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
mainatf9f7feba8e7bb499c6001bf0cc19a38357b7494aon 2026-09-27.Why this element
The book cover is one of the few visual elements whose identity genuinely persists across:
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:
Back:
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
Accessibility / reduced motion
Acceptance
This issue is explicitly optional polish. The app must feel coherent without it.