Task flow and content structure

Write success, empty, and recovery flows before drawing pages.

Difficulty
beginner
Time
45 minutes
Last verified
9/21/2026

What you will build

Write success, empty, and recovery flows before drawing pages.

Understand the idea first

Write success, empty, and recovery flows before drawing pages.

Build it step by step

首次进入 → 看见空状态 → 添加记录 → 看见进度
失败:输入无效 → 就地提示 → 修改后成功
恢复:数据请求失败 → 保留已有记录 → 重试
  1. Open the previous project and record its result.
  2. Type the example and complete: Run a paper prototype, record three hesitations, and revise copy or order.
  3. Change one input, predict, then verify.
  4. Create and repair: Do not polish a homepage first; prove the core task connects end to end.

Read the important lines

  • Write success, empty, and recovery flows before drawing pages.
  • Read input, processing, and output separately.
  • Verify another input and an edge case.

Common mistakes and what to check

SymptomWhat to check
Unexpected resultDo not polish a homepage first; prove the core task connects end to end.
Nothing changesSave, verify paths, and read the first relevant Console error.

Practice without copying

Run a paper prototype, record three hesitations, and revise copy or order.

Check the answer after you try

Rebuild and explain the decisions. Check: Do not polish a homepage first; prove the core task connects end to end.

Completion check

  • I produced the required visible result
  • I can explain the input, processing, and output
  • I tested normal, edge, and failure cases

Your privacy choices

Necessary storage is always on. Optional analytics and support services load only after consent.