classic+ UX: typography and spacing polish #3
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?
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.yamlbroadly; may also apply todisplay-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.