Name the user-side action
Button labels such as Save changes or Clear search are easier to predict than vague labels such as Continue or Submit. Technical details belong in logs unless the user needs them to decide or recover.
Feedback follows the action
Loading feedback should appear when waiting changes what the user can do. Success should confirm the meaningful outcome, and errors should distinguish a fixable input problem from a service failure.
A familiar example
Handling an empty search
- The page says no lesson matched the entered term.
- It suggests broader beginner topics.
- A Clear search action restores the complete curriculum and returns focus to the field.
What to remember
- Prefer plain action labels over internal terminology.
- Feedback should match the user's current decision or wait.
- Every recoverable error needs a clear next step.