[Hallmark] Establish a coherent app-wide navigation and motion language #101
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
Define and implement a small, consistent navigation/motion vocabulary for BookWave so transitions explain hierarchy without making the app feel animated for its own sake.
This is the parent/staging issue for app-wide route motion. Focused player expansion is tracked separately. Existing Home/Settings visual redesign issues remain authoritative for their local UI.
Reviewed against current
mainatf9f7feba8e7bb499c6001bf0cc19a38357b7494aon 2026-09-27.Design principle
BookWave should use motion to explain where the user is going:
Avoid decorative bounce, gratuitous parallax, full-screen theatrical slides and unrelated one-off animation specs.
1. Add shallow route-depth transitions
The current
ShelfPlayerNavHostdefines routes without an explicit BookWave transition contract.Prototype a restrained push/pop treatment for detail navigation such as:
Preferred feel:
Utility destinations such as Profiles / Settings / Downloads may use a quieter fade or very shallow movement because they represent a task change rather than deeper content hierarchy.
2. Support predictive Back
Where Android/Navigation Compose supports it, route transitions should track predictive-back progress instead of waiting for gesture completion.
Requirements:
Do not break existing navigation-stack semantics or sign-in
popUpTobehavior.3. Establish a tiny shared motion vocabulary
Create/reuse semantic animation specs rather than choosing spring/tween behavior independently in each screen.
Suggested roles to prototype, not hard-coded release values:
Rule:
4. Reduced-motion contract
Verify all BookWave-owned spatial motion with Android animation/motion scale reduced or disabled.
Reduced motion must preserve:
Continuous decorative motion should stop or collapse where the platform requests reduced motion. Functional progress indicators may remain functional.
Explicitly verify:
Do not add a BookWave-specific Reduce Motion preference unless platform behavior proves insufficient.
5. Keep good gesture-driven motion
Preserve the current Home axis design:
Preserve edge resistance as feedback at pager bounds, subject to #95's separate persistent-nav bounce cleanup.
Implementation starting points
app/src/main/kotlin/com/example/shelfplayer/navigation/ShelfPlayerNavHost.ktapp/src/main/kotlin/com/example/shelfplayer/ui/gesture/EdgeOverspill.ktDo not refactor unrelated navigation architecture merely to centralize animation values.
Acceptance
This issue defines the app-wide language. Child/local issues should consume it rather than inventing competing motion systems.
Related focused issues
Consume rather than duplicate these local owners:
#101 owns the shared vocabulary and route-level behavior, not those screens' visual redesigns.
Hallmark Slice 1 — player-only subset adopted
This slice consumes only the player subset of #101:
No app-wide route transitions, Home/Book navigation changes, Settings motion or sign-in navigation work are included. #101 remains open as the parent contract.
Hallmark Slice 1 — implemented player subset
Branch
mcp/hallmark-slice-1-playernow consumes the player-only portion of #101 at HEADf4f90f10a624e310cb87d6abe20482aea444bcb2:No Home→Book, Settings, Sign-in or other app-wide navigation transition work was included. #101 remains open.
Hallmark code-level review: Philosophy 5/5 · Hierarchy 5/5 · Execution 4/5 · Specificity 5/5 · Restraint 5/5 · Variety 4/5. Execution is intentionally held below 5 because rendered/device acceptance was not run under the owner's no-checks instruction.