From d35d1159b7a354c8ec3d97633486879aa3093e2e Mon Sep 17 00:00:00 2001 From: leavy Date: Thu, 11 Jun 2026 01:55:43 +0800 Subject: [PATCH] docs: require dynamic UI state stress tests --- launch/roadmaps/v1.0.1-experience-brief.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/launch/roadmaps/v1.0.1-experience-brief.md b/launch/roadmaps/v1.0.1-experience-brief.md index db26a70..139c19b 100644 --- a/launch/roadmaps/v1.0.1-experience-brief.md +++ b/launch/roadmaps/v1.0.1-experience-brief.md @@ -69,6 +69,15 @@ Each route must show how its visual choices improve: - Accessibility, localization, dark mode, and responsive layouts - Smooth rendering and restrained battery use on ordinary Android devices +Every route must also be designed as a stateful product system, not as a static poster. Stress-test the same visual language with: + +- Empty, first-use, populated, loading, saving, success, recoverable error, and destructive-confirmation states +- Timer idle, running, paused, background-restored, completed, and interrupted states +- Zero, one, several, completed, archived, and long-named habits +- Short and long anchors, translated text expansion, large system text, RTL, and narrow/wide layouts +- Dynamic list growth, scrolling, keyboard appearance, safe areas, and bottom-navigation persistence +- Content changes that must not cause layout jumps, clipped actions, hidden status, or accidental taps + Evaluate the three routes with the same weighted scorecard: - Usability and task clarity: 30% @@ -94,6 +103,7 @@ The chosen visual route must define: - Motion curves and durations - Light/dark behavior - Localization and text-expansion behavior +- Component behavior across data density, asynchronous state, lifecycle restoration, and content growth ## 1.0.1 Priority Order @@ -153,6 +163,7 @@ Preferred order: - The timer remains correct through backgrounding and restoration. - Main actions respond immediately and consistently. - No screen overflows at supported text scales and locales. +- Empty, dense, loading, error, long-content, and lifecycle-restored states preserve hierarchy and access to the primary action. - Users can explain the Daily Anchor Loop after one session. - Testers return without being prompted solely for testing compliance. - Visual identity is recognizable without sacrificing clarity or performance.