[Hallmark] Reduce Home chrome density and give shelves distinct visual roles #95
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 Home screen hierarchy without changing its established BookWave identity.
Parent design direction: #48. Related dedicated work: #49 owns the leading Continue listening card; #50 owns the flat Books list. This issue deliberately does not duplicate those scopes.
Reviewed against current
mainatf9f7feba8e7bb499c6001bf0cc19a38357b7494aon 2026-09-27.Product direction
Keep:
The goal is calmer hierarchy, not a navigation rebuild.
Changes to prototype
1. Reduce permanent toolbar density
The current Home top bar can show Search, Books view toggle, Refresh and Overflow together.
Keep the permanent global actions to:
Move the Shelves/List view choice into the Books content because it changes the representation of Books rather than the application globally. It should remain obvious and accessible without opening an unrelated menu.
Do not remove the explicit refresh action; pull-to-refresh remains a gesture alternative, not its replacement.
2. Differentiate shelf roles
Do not render every Home shelf as the same visual rhythm merely with different content.
Use spacing, card measure and text hierarchy to distinguish intent. Do not introduce arbitrary card sizes, marketing-style hero treatment, decorative badges or extra gradients.
3. Restrain perpetual motion
Current compact shelf cards can marquee author, title and series independently.
Prototype:
Full metadata remains available in the Book screen and accessibility semantics.
Responsive requirements
Acceptance
This issue is presentation-only unless implementation uncovers a behavior defect; record such a defect separately rather than silently changing library or playback policy.
2026-09-27 navigation/motion audit refinement
The Home pager/pill motion is intentionally kept: both follow the user's drag directly and already communicate sibling library axes well.
One additional accepted refinement belongs in this issue:
HomeAxisBarMotionStatecurrently gives the entire persistent navigation capsule an under-damped return (RETURN_DAMPING_RATIO = 0.46f) so it passes its resting point.App-wide motion vocabulary/predictive Back is now staged in #101.