Course progress: 0 / 20 lessons

LESSON 16 OF 20

Dynamic updates

Modern interfaces change without a full page load. Users need to know what changed without having their current task repeatedly interrupted.

  • Reading: about 2 minutes
  • Knowledge check: 2-3 minutes
  • Optional practice: 6 exercises, 5-15 minutes each
In this lesson

Choose suitable focus and announcement behavior for status, loading, notifications, timeouts, routes, and inserted results.

Separate context changes from status updates

A new route or dialog may need deliberate focus movement. A background save or result count usually needs an announcement that preserves focus.

Communicate progress and completion

Loading indicators should expose that work started and, when useful, that it completed. Animation alone does not provide this information.

Make temporary information usable

Toasts and timeout warnings need enough persistence, priority, and controls for users to understand and act on them.

Preserve the user's place

When results or content are inserted, communicate the update while keeping navigation predictable. Do not force users to rediscover where they were.

What to remember

Use focus for a genuine change of interaction context and announcements for relevant updates that should not take control away.

Knowledge check

Answer every question, then use the forward lesson button to record this lesson as complete. The check is not scored and can be repeated.

1. When should a status message move focus?

2. What should a route change in a single-page app establish?

NEXT STEP

Continue to lesson 17: Controls and navigation

Move on when you are ready. Your knowledge-check answers are not stored.