Check: recovery, safety, and accessibility

Knowledge check · self-test
Check: recovery, safety, and accessibility
You now know: - For slow mechanical actions, show the transition state immediately, then confirm the final state after the device reports it. - A failed command should revert or mark uncertainty, not leave the optimistic state looking final. - Duplicate commands, obstruction, sensor failure, and network timeout need different messages because each asks for a different next action. You now know: - Pending and confirmed states must look and read differently, especially for locks, alarms, pumps, heaters, and access control. - Accessibility is part of the state machine: do not rely on color alone, use text labels, and announce important status changes. - A muted notification, dismissed notification, acknowledged incident, and resolved event are separate states, so store and display them separately.
You now know: - For slow mechanical actions, show the transition state immediately, then confirm the final state after the device reports it. - A failed command should revert or mark uncertainty, not leave the optimistic state looking final. - Duplicate commands, obstruction, sensor failure, and network timeout need different messages because each asks for a different next action. You now know: - Pending and confirmed states must look and read differently, especially for locks, alarms, pumps, heaters, and access control. - Accessibility is part of the state machine: do not rely on color alone, use text labels, and announce important status changes. - A muted notification, dismissed notification, acknowledged incident, and resolved event are separate states, so store and display them separately.