LOOK UP WHEN NEEDED
State
Data and conditions determining current behavior.
An everyday example
A counter can be open, busy, or paused.
See how these concepts connect
- Submit orderButton action
- PreparingLoading
- Unavailable: choose againError & recovery
- Order confirmedSuccess
This is one possible failure-and-recovery path, not a mandatory failure. Explain what is happening and offer usable recovery.
Where this term is useful
These are related contexts, not prerequisites.
Back in the project
When it comes up: When interacting with controls, loading, or handling errors.
What to do next: Specify what appears, available actions, and recovery in each state.
Open the related method and stepsWhat can this analogy leave out?
Success feedback must reflect reality; hiding a control is not server authorization.
Everyday examples explain roles and relationships; actual behavior follows the tool, language, or platform.