Design: define consistent empty, error, and permission copy across search, stop, route, and map screens

[github-world192]

Problem

Search, stop detail, route planning, and map screens handle missing data and permission failures differently. This creates a fragmented product voice and makes it harder for users to recover.

Product design direction

Create a shared UX pattern for non-happy paths:

• Empty: what happened and what the user can try next
• Error: what failed, whether data may be stale, and how to retry
• Permission denied: what feature needs permission and where to go next
• Loading: neutral progress copy without implying failure

Acceptance criteria

• Each core screen has reviewed copy for loading, empty, denied, and error states.
• Recovery actions are explicit: retry, search, map, back, or change route.
• Copy avoids blame and does not expose implementation details.
• Tone and terminology are consistent across the app.
• States are documented in a small design note or component comments for future reuse.

Senior design advice

The app's best UX improvements are likely in recovery paths, not decoration. Riders will forgive missing data if the app tells them clearly what happened and gives them a next step.