classic+ UX: typography and spacing polish #3

Open
opened 2026-07-12 22:31:20 -07:00 by pyr0ball · 0 comments
Owner

Gap: touch targets are inconsistent across the classic+ Home screen (36px mode-toggle buttons vs 60px quick-actions rail buttons vs 90x60 dial value buttons vs 400x400 arcs). Only 5 fixed Montserrat sizes in use (16/20/24/28/32/48) with no clear hierarchy system, and spacing is ad hoc per-widget x/y offsets rather than a consistent scale.

Scope: define a consistent spacing scale and touch-target minimum (elderly-user accessibility consideration — this UI's whole purpose is the zero-relearning-curve, adaptive-needs use case), establish a clear text-size hierarchy (primary reading vs secondary/label text), audit color contrast. Likely touches display-classic-plus.yaml broadly; may also apply to display-classic.yaml (classic variant) where the same widgets are shared conceptually, though classic must stay strictly Lennox-faithful so any change there needs separate justification against the reference photos.

**Gap:** touch targets are inconsistent across the classic+ Home screen (36px mode-toggle buttons vs 60px quick-actions rail buttons vs 90x60 dial value buttons vs 400x400 arcs). Only 5 fixed Montserrat sizes in use (16/20/24/28/32/48) with no clear hierarchy system, and spacing is ad hoc per-widget x/y offsets rather than a consistent scale. **Scope:** define a consistent spacing scale and touch-target minimum (elderly-user accessibility consideration — this UI's whole purpose is the zero-relearning-curve, adaptive-needs use case), establish a clear text-size hierarchy (primary reading vs secondary/label text), audit color contrast. Likely touches `display-classic-plus.yaml` broadly; may also apply to `display-classic.yaml` (classic variant) where the same widgets are shared conceptually, though classic must stay strictly Lennox-faithful so any change there needs separate justification against the reference photos.
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: Circuit-Forge/firecrest#3
No description provided.