[Hallmark] Refine Settings navigation and separate everyday settings from diagnostics #99
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
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
mainatf9f7feba8e7bb499c6001bf0cc19a38357b7494aon 2026-09-27.Keep
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:
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:
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:
Move or group low-frequency engineering/testing material under that advanced surface:
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
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:
The shared app-wide route/motion contract is staged in #101.