[Hallmark] Reduce Home chrome density and give shelves distinct visual roles #95

Open
opened 2026-09-27 13:48:46 +02:00 by alexander · 1 comment
Owner

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

Product direction

Keep:

  • the frosted top chrome;
  • swipeable Books / Series / Authors / Genres pages;
  • the moving frosted bottom-axis capsule;
  • cover-led shelves and current navigation behavior.

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:

  • Search;
  • Refresh / sync state;
  • More.

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.

  • Continue listening: owned by #49; this remains the strongest resume surface.
  • Continue series: retain series-specific identity and next-book context.
  • Recently added: compact, cover-led and quiet.
  • Listen again: compact and lower visual priority than active listening.
  • Discover: compact browsing surface, not a second hero.

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:

  • title may marquee only when necessary, preferably after a short delay;
  • author and series remain static and ellipsize/wrap according to the final card geometry;
  • reduced-motion mode must provide a fully usable static treatment;
  • multiple visible cards should not create several continuously moving text lines.

Full metadata remains available in the Book screen and accessibility semantics.

Responsive requirements

  • Preserve readable Home chrome at 320 / 375 / 414 / 768 dp.
  • Long Norwegian/English labels and font scales through 2.0 must not force important actions out of reach.
  • The Books view control must stay understandable when moved into content.
  • The mini-player and bottom navigation clearance behavior remains intact.
  • Tablet layouts should retain a readable content measure rather than stretching shelves simply because width exists.

Acceptance

  • Home retains the current BookWave glass/backdrop identity and swipe/navigation behavior.
  • Search, refresh and overflow remain immediately reachable.
  • Shelves/List is clearly associated with Books and remains one-tap or equivalently direct.
  • Different shelf types have deliberate visual roles without random asymmetry.
  • Visible shelf metadata is calmer than the current multi-marquee presentation.
  • Validate light, dark, AMOLED and background packs; reduced motion; TalkBack; missing artwork; long metadata; active playback; offline/cached state.
  • Compare rendered before/after screenshots at representative widths before 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.

## 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 `main` at `f9f7feba8e7bb499c6001bf0cc19a38357b7494a` on 2026-09-27. ## Product direction Keep: - the frosted top chrome; - swipeable Books / Series / Authors / Genres pages; - the moving frosted bottom-axis capsule; - cover-led shelves and current navigation behavior. 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: - Search; - Refresh / sync state; - More. 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. - Continue listening: owned by #49; this remains the strongest resume surface. - Continue series: retain series-specific identity and next-book context. - Recently added: compact, cover-led and quiet. - Listen again: compact and lower visual priority than active listening. - Discover: compact browsing surface, not a second hero. 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: - title may marquee only when necessary, preferably after a short delay; - author and series remain static and ellipsize/wrap according to the final card geometry; - reduced-motion mode must provide a fully usable static treatment; - multiple visible cards should not create several continuously moving text lines. Full metadata remains available in the Book screen and accessibility semantics. ## Responsive requirements - Preserve readable Home chrome at 320 / 375 / 414 / 768 dp. - Long Norwegian/English labels and font scales through 2.0 must not force important actions out of reach. - The Books view control must stay understandable when moved into content. - The mini-player and bottom navigation clearance behavior remains intact. - Tablet layouts should retain a readable content measure rather than stretching shelves simply because width exists. ## Acceptance - Home retains the current BookWave glass/backdrop identity and swipe/navigation behavior. - Search, refresh and overflow remain immediately reachable. - Shelves/List is clearly associated with Books and remains one-tap or equivalently direct. - Different shelf types have deliberate visual roles without random asymmetry. - Visible shelf metadata is calmer than the current multi-marquee presentation. - Validate light, dark, AMOLED and background packs; reduced motion; TalkBack; missing artwork; long metadata; active playback; offline/cached state. - Compare rendered before/after screenshots at representative widths before 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.
Author
Owner

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:

  • HomeAxisBarMotionState currently gives the entire persistent navigation capsule an under-damped return (RETURN_DAMPING_RATIO = 0.46f) so it passes its resting point.
  • Replace that decorative overshoot with either a stationary capsule or a very small inertial drift that returns without bounce.
  • Preserve the edge-overspill resistance/snap-back gesture: that is direct physical feedback at a pager boundary and is a different motion role.

App-wide motion vocabulary/predictive Back is now staged in #101.

## 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: - `HomeAxisBarMotionState` currently gives the entire persistent navigation capsule an under-damped return (`RETURN_DAMPING_RATIO = 0.46f`) so it passes its resting point. - Replace that decorative overshoot with either a stationary capsule or a very small inertial drift that returns **without bounce**. - Preserve the edge-overspill resistance/snap-back gesture: that is direct physical feedback at a pager boundary and is a different motion role. App-wide motion vocabulary/predictive Back is now staged in #101.
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#95
No description provided.