Error Recovery Paths
Every error state tells users what went wrong and provides a specific next action.
Check
Every error message: (1) states what went wrong in plain language, (2) explains why if not obvious, (3) provides a specific action button (Retry, Go back, Contact support). No error shows only a code or generic "Something went wrong".
Why This Matters
Errors without recovery paths create dead ends. Users who cannot recover abandon the product. An error with a clear next step is a recoverable experience; an error without one is a failure.
Category
Error Handling
Priority
important
How to Verify
Disconnect network and trigger every data-loading view. Check: does each error state tell users what happened AND what to do next? Test 404, 500, network offline, and session expired scenarios.