UX Requirements
Owner: Product Design
Reviewers: Product, Web, Mobile, QA
Status: Draft
Version: 0.1
Last Updated: 2026-09-16
Review Cycle: Per feature/release
Requirements
| ID | Requirement | Surface | Status |
|---|---|---|---|
| UX-01 | Role-specific navigation must expose only relevant workflows. | Web/Mobile | PARTIAL |
| UX-02 | Entity list/detail pages must support scan-friendly tables or cards. | Web/Mobile | PARTIAL |
| UX-03 | Farm/pond context must stay visible for operational actions. | Web/Mobile | PARTIAL |
| UX-04 | Alerts and incidents must show severity, status and next action. | Web/Mobile | PARTIAL |
| UX-05 | Forms must validate required fields before API submission. | Web/Mobile | PARTIAL |
| UX-06 | Placeholder features must not imply production-ready behavior. | Web/Mobile | PARTIAL |
| UX-07 | Mobile technician flows must support field usage with concise actions. | Mobile | PARTIAL |
Current Constraints
- Web uses Ant Design and feature-oriented pages.
- Mobile uses Expo, React Navigation, React Native UI and role-based tabs.
- Several feature screens are placeholders or partial, so UX copy should avoid claiming unsupported functionality.