docs: define scroll-first Today workspace

2026-06-11 02:47:40 +08:00
parent 72e7ec0c0b
commit c51abdfb73
1 changed files with 14 additions and 1 deletions
@@ -43,7 +43,7 @@ Every design decision must pass these five product-level requirements:
 ### Functional Discoverability And Copy
-The Today screen is a compact daily workspace. It must reveal the complete core loop without presenting every feature at equal visual strength:
+The Today screen is a vertically scrollable daily workspace. It must make the complete core loop discoverable across the page without forcing every module into the first viewport or presenting every feature at equal visual strength:
 1. Anchor: today's chosen task and edit action.
 2. Focus: duration, current timer state, and the single P0 action.
@@ -66,6 +66,19 @@ Module rules:
 - Keep Focus visually dominant; Anchor provides context; Habits and Reflect are secondary; progress decoration is tertiary.
 - Never repeat the same task, timer value, or progress metric in multiple modules on one screen.
 - Show enough function to explain what the app can do, then use progressive disclosure for full lists, history, settings, and detailed input.
 - Size modules from their content and constraints rather than forcing them into one fixed screen height.
 - The first viewport should show Anchor and Focus completely. When space permits, reveal the next module heading or a small content edge as an honest scroll cue; never compress core controls merely to create that cue.
 - Habits and Reflect may appear later in the scroll flow. Their navigation destinations, section cues, and consistent ordering provide discovery without requiring simultaneous visibility.
 Scroll and transition rules:
 - Use natural vertical scrolling with a fixed bottom navigation. Do not hijack scrolling, force section snapping, or use decorative parallax.
 - Let the large header collapse quietly as content moves, preserving useful vertical space.
 - Before a session starts, Focus remains an ordinary dominant module in document flow.
 - While a session is running or paused, transform Focus into a compact pinned session bar that keeps time, Pause/Resume, and Finish accessible while the user reviews habits or reflection.
 - Keep the pinned session bar compact enough that it does not obscure module headings, keyboard content, system insets, or the bottom navigation.
 - Preserve scroll position and module expansion state when switching destinations or returning from the timer flow where practical.
 - Use scroll-linked motion only to explain hierarchy or continuity. Reduced-motion mode uses immediate state changes without losing information.
 ### Supporting Rules