Skip to content

Check: synchronization and immediate feedback

Knowledge check · self-test

Check: synchronization and immediate feedback

You now know: - Commands need ids so retries do not create duplicate physical actions; pending commands need a timeout path such as 10 seconds. - Polling at 30 or 60 seconds can leave a stale interface for up to that interval; this design targets roughly 1–2-second cross-interface updates with push transport. - Support evidence should use the UI vocabulary, so "timeout," "offline," "confirmed," and "changed while offline" mean the same thing in logs and screens.

Back to the chapter →

You now know: - Commands need ids so retries do not create duplicate physical actions; pending commands need a timeout path such as 10 seconds. - Polling at 30 or 60 seconds can leave a stale interface for up to that interval; this design targets roughly 1–2-second cross-interface updates with push transport. - Support evidence should use the UI vocabulary, so "timeout," "offline," "confirmed," and "changed while offline" mean the same thing in logs and screens.

Back to Interaction Patterns: Synchronization and Recovery