首次远程推送
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Focus Seed Visual System v1.0.2
|
||||
|
||||
Status: planning contract. Do not treat this document as an implementation diff.
|
||||
Status: visual direction reference. Current product scope is defined in `../product-current-baseline.md`.
|
||||
|
||||
## Product Thesis
|
||||
|
||||
@@ -31,14 +31,14 @@ This direction is global-friendly, feasible in Flutter, serious enough for produ
|
||||
|
||||
## Target App Structure
|
||||
|
||||
Preferred primary navigation:
|
||||
Current V1 primary navigation:
|
||||
|
||||
- Today: daily action hub.
|
||||
- Focus: immersive timer and active session.
|
||||
- Habits: habit list, completion, weekly rhythm.
|
||||
- Growth: reflection, history, trends, milestones.
|
||||
- Records: focus sessions and reflection history.
|
||||
- Me: preferences, privacy, and local data controls.
|
||||
|
||||
Settings should move behind a top-right profile/settings entry or a More sheet. It should not compete with the daily loop unless account, billing, or preferences become a core product surface.
|
||||
Habits and Growth are not current primary tabs. They can be promoted later only when habit management, trend review, and detail pages are real product surfaces rather than thin wrappers.
|
||||
|
||||
## Screen Hierarchy
|
||||
|
||||
@@ -46,18 +46,22 @@ Settings should move behind a top-right profile/settings entry or a More sheet.
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| Today | Know what to do now | Date, greeting, main focus | Start focus or set focus | Habit summary, reflection prompt, small growth cue | Natural vertical scroll; P0 remains near top |
|
||||
| Focus | Stay in one session | Current task and timer | Pause/complete/start | Duration, mode, next break, session stats | Minimal scroll; controls stable |
|
||||
| Habits | Complete and manage habits | Today progress and filters | Toggle habit / add habit | Weekly dots, streaks, edit/reorder | Dense list; sticky section controls optional |
|
||||
| Growth | Understand progress | Reflection entry or weekly summary | Reflect today / view timeline | Sessions, habits, records, trend charts | Timeline + cards; history can go to detail |
|
||||
| Settings | Adjust app and privacy | Local data, appearance, language | Change preference | Privacy, clear data, version | Compact grouped list |
|
||||
| Records | Review saved work | Focus/reflection history switch | Open Today when empty | Sessions, notes, simple trends | Timeline/list; detail pages are V2 |
|
||||
| Me | Adjust app and privacy | Local data summary | Change preference | Privacy, clear data, language | Compact grouped list |
|
||||
|
||||
## Visual System
|
||||
|
||||
Palette:
|
||||
|
||||
- Primary: mature green or teal for progress and focus.
|
||||
- Secondary: restrained blue/violet for reflection or insight.
|
||||
- Brand: deep ink for identity, headings, and logo text. Do not use brand as a catch-all accent.
|
||||
- Action: blue for primary buttons, navigation selection, and forward movement.
|
||||
- Focus: blue family for timer and active-session controls.
|
||||
- Habit: amber or warm accent for small repeatable actions.
|
||||
- Reflection: violet for notes, review, and insight.
|
||||
- Success: green for completion, checkmarks, and finished progress.
|
||||
- Privacy/local: green-teal for on-device trust indicators only.
|
||||
- Warm neutral surfaces instead of pure white where appropriate.
|
||||
- Semantic colors for success, warning, destructive, disabled, offline.
|
||||
- Warning/destructive/disabled/offline must remain separate semantic colors.
|
||||
- Dark mode must be designed, not inverted.
|
||||
|
||||
Typography:
|
||||
@@ -79,6 +83,14 @@ Motifs:
|
||||
- Use illustration in empty states, onboarding, growth, and rewards.
|
||||
- Do not decorate every card.
|
||||
|
||||
Asset ambition:
|
||||
|
||||
- Be more expressive with the logo, app icon, key illustration set, reward visuals, and store screenshots. These are allowed to carry stronger identity than the everyday UI.
|
||||
- Do not rely only on the plant metaphor. Explore sharper symbols such as focus rings, marked paths, light windows, paper cuts, modular tiles, timeline traces, and crafted seed/anchor hybrids.
|
||||
- Navigation and utility icons should stay readable and consistent, but they may use a custom symbolic grammar after the structure passes.
|
||||
- Illustrations should feel complete and production-worthy at their real display size. Avoid rough placeholder line art in polished previews.
|
||||
- Dense task surfaces stay restrained; onboarding, empty states, milestones, completion moments, and launch assets can be bolder.
|
||||
|
||||
## Interaction And Motion
|
||||
|
||||
Motion budget:
|
||||
@@ -87,6 +99,12 @@ Motion budget:
|
||||
- 15% spatial motion: tab/page/sheet/list transitions.
|
||||
- 5% reward: session complete, streak, milestone.
|
||||
|
||||
Motion ambition:
|
||||
|
||||
- Reward moments may be more memorable than the base UI: focus ring bloom, path lighting, notebook mark, seed-to-signal transition, or timeline pulse.
|
||||
- Keep bold motion rare, interruptible, and non-blocking. It should celebrate completion or clarify state, not decorate every tap.
|
||||
- Use Flutter-safe primitives first. Escalate to Rive/Lottie only for a signature reward or onboarding moment with a static fallback and reduced-motion behavior.
|
||||
|
||||
Required behavior:
|
||||
|
||||
- Tap feedback within 100 ms.
|
||||
@@ -127,9 +145,9 @@ Create or consolidate:
|
||||
|
||||
1. Create design, component, and motion foundations.
|
||||
2. Prototype Today and Focus first; review screenshots and interaction.
|
||||
3. Add the Habits screen as a real first-class surface.
|
||||
4. Rework Growth into reflection plus progress timeline.
|
||||
5. Move Settings out of primary navigation or make it compact.
|
||||
3. Keep Records and Me honest until Habits/Growth have enough product depth to become primary tabs.
|
||||
4. Add detail pages only when they have data writes, navigation targets, and clear user outcomes.
|
||||
5. Keep Settings compact and user-facing; avoid developer-tool language.
|
||||
6. Add empty/dense/error/offline/restored states.
|
||||
7. Verify light/dark, English/Chinese, small phone, large text.
|
||||
8. Build and test Android release after each large module.
|
||||
|
||||
Reference in New Issue
Block a user