[Hallmark] Refine Settings navigation and separate everyday settings from diagnostics #99

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

Purpose

Make Settings easier to orient in and quieter to scan while preserving the existing settings model and the successful Appearance controls.

Related direction: #48 covers Appearance specifically; this issue owns the broader Settings shell and non-Appearance information hierarchy.

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

Keep

  • Appearance → Playback → Server → About as the main conceptual groups.
  • Swipe/tap navigation where it remains useful.
  • Existing appearance choices, inline disclosure and swatch semantics.
  • Current settings ownership, repositories and behavior.
  • BookWave backdrop/frosted header treatment.

1. Make location explicit

The current top chrome is only the tab strip, with three icon-only tabs and a text-only About tab.

Prototype a clearer Settings identity:

  • an explicit Settings/back affordance in the header;
  • consistent category treatment rather than three icons plus one unrelated word;
  • short icon + label treatment when width allows;
  • compact selected-category labeling on narrow screens if all labels cannot fit.

Do not make important category names discoverable only through TalkBack.

On larger windows/tablets, evaluate a left navigation rail/list so the content pane keeps a readable measure instead of stretching a four-tab phone layout.

2. Use containment selectively

Keep glass/card grouping where it genuinely groups interactive settings, especially Appearance compound controls.

For informational Server/About/diagnostic readings:

  • prefer flatter sections, spacing and hairline separation;
  • avoid wrapping every small fact in equally prominent glass containers;
  • preserve clear selected/pressed/focus states for actual controls.

3. Separate consumer settings from diagnostic depth

About currently carries app identity plus Event Log, Debug Console, playback metrics, testing data, storage/capability state and system integration diagnostics.

Keep a concise everyday About surface:

  • app/version/build identity as appropriate;
  • launcher/icon identity;
  • a clear Advanced & diagnostics entry.

Move or group low-frequency engineering/testing material under that advanced surface:

  • event log;
  • debug console;
  • playback metrics where diagnostic rather than user-facing;
  • testing/capability readings;
  • storage diagnostics;
  • notification/car/session-sync diagnostics.

Do not remove data required for acceptance or support; change its hierarchy.

Debug-only controls remain debug-only.

4. Settings typography and numeric stability

Use existing semantic Material typography, but establish clear section/header/body roles rather than allowing every row equal visual weight.

Use tabular figures for metric/time values that update or align vertically.

Acceptance

  • A user can identify that they are in Settings and navigate back without relying on a hidden gesture.
  • Appearance / Playback / Server / About are named consistently and remain reachable by tap; swipe behavior may remain as an additional interaction.
  • No category label becomes unreadable at 320/375/414dp or large text.
  • Tablet/wide layout remains readable and does not leave label/control pairs a hand-span apart.
  • Common settings remain visually above diagnostic/testing material.
  • All current diagnostic surfaces remain reachable.
  • Verify light/dark/AMOLED/background packs, TalkBack, font scales through 2.0, narrow/landscape/tablet windows and mini-player clearance.
  • Preserve settings persistence and behavior; this is a presentation/information-architecture issue, not a settings-domain rewrite.
## Purpose Make Settings easier to orient in and quieter to scan while preserving the existing settings model and the successful Appearance controls. Related direction: #48 covers Appearance specifically; this issue owns the broader Settings shell and non-Appearance information hierarchy. Reviewed against current `main` at `f9f7feba8e7bb499c6001bf0cc19a38357b7494a` on 2026-09-27. ## Keep - Appearance → Playback → Server → About as the main conceptual groups. - Swipe/tap navigation where it remains useful. - Existing appearance choices, inline disclosure and swatch semantics. - Current settings ownership, repositories and behavior. - BookWave backdrop/frosted header treatment. ## 1. Make location explicit The current top chrome is only the tab strip, with three icon-only tabs and a text-only About tab. Prototype a clearer Settings identity: - an explicit Settings/back affordance in the header; - consistent category treatment rather than three icons plus one unrelated word; - short icon + label treatment when width allows; - compact selected-category labeling on narrow screens if all labels cannot fit. Do not make important category names discoverable only through TalkBack. On larger windows/tablets, evaluate a left navigation rail/list so the content pane keeps a readable measure instead of stretching a four-tab phone layout. ## 2. Use containment selectively Keep glass/card grouping where it genuinely groups interactive settings, especially Appearance compound controls. For informational Server/About/diagnostic readings: - prefer flatter sections, spacing and hairline separation; - avoid wrapping every small fact in equally prominent glass containers; - preserve clear selected/pressed/focus states for actual controls. ## 3. Separate consumer settings from diagnostic depth About currently carries app identity plus Event Log, Debug Console, playback metrics, testing data, storage/capability state and system integration diagnostics. Keep a concise everyday About surface: - app/version/build identity as appropriate; - launcher/icon identity; - a clear **Advanced & diagnostics** entry. Move or group low-frequency engineering/testing material under that advanced surface: - event log; - debug console; - playback metrics where diagnostic rather than user-facing; - testing/capability readings; - storage diagnostics; - notification/car/session-sync diagnostics. Do not remove data required for acceptance or support; change its hierarchy. Debug-only controls remain debug-only. ## 4. Settings typography and numeric stability Use existing semantic Material typography, but establish clear section/header/body roles rather than allowing every row equal visual weight. Use tabular figures for metric/time values that update or align vertically. ## Acceptance - A user can identify that they are in Settings and navigate back without relying on a hidden gesture. - Appearance / Playback / Server / About are named consistently and remain reachable by tap; swipe behavior may remain as an additional interaction. - No category label becomes unreadable at 320/375/414dp or large text. - Tablet/wide layout remains readable and does not leave label/control pairs a hand-span apart. - Common settings remain visually above diagnostic/testing material. - All current diagnostic surfaces remain reachable. - Verify light/dark/AMOLED/background packs, TalkBack, font scales through 2.0, narrow/landscape/tablet windows and mini-player clearance. - Preserve settings persistence and behavior; this is a presentation/information-architecture issue, not a settings-domain rewrite.
Author
Owner

2026-09-27 navigation/motion audit refinement

Keep the existing pull-past-start gesture as an optional shortcut, but do not let it remain the only visible Settings exit. This reinforces this issue's existing requirement for an explicit Settings/back affordance.

Also evaluate category switching once the labelled navigation is redesigned:

  • Settings may retain horizontal swipe as a convenience;
  • tapping a distant category should feel quicker/quieter than physically travelling through every intermediate tab;
  • do not make Settings as spatially strong as the Home Books/Series/Authors/Genres pager.

The shared app-wide route/motion contract is staged in #101.

## 2026-09-27 navigation/motion audit refinement Keep the existing pull-past-start gesture as an optional shortcut, but do not let it remain the only visible Settings exit. This reinforces this issue's existing requirement for an explicit Settings/back affordance. Also evaluate category switching once the labelled navigation is redesigned: - Settings may retain horizontal swipe as a convenience; - tapping a distant category should feel quicker/quieter than physically travelling through every intermediate tab; - do not make Settings as spatially strong as the Home Books/Series/Authors/Genres pager. The shared app-wide route/motion contract is 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#99
No description provided.