Ship the delivery platform UI under modules/delivery with thin app routes, BFF proxy, CRUD for phase 10.0-10.1 APIs, and capability-gated future screens. Co-authored-by: Cursor <cursoragent@cursor.com>
2.0 KiB
2.0 KiB
Delivery UI Checklist
Per-screen requirements for Torbat Driver frontend.
Global (every screen)
- Loading state (
loading.tsx+ in-page loader) - Error state (
error.tsx+DeliveryPageError) - Empty state (
DeliveryEmptyState/ DSEmptyState) - Permission state (
PermissionDeniedState) - Responsive layout (mobile drawer + desktop sidebar)
- Breadcrumb (where applicable)
- RTL layout
- Dark mode tokens
Live CRUD screens
Organizations /delivery/organizations
- List, create, edit, delete
- Search, pagination, CSV export
- Status badges
- Permission check
Branches /delivery/branches
- Organization selector on create
- Full CRUD
- API: hubs
Drivers /delivery/drivers
- Paginated list
- Link to detail
- Create with org/hub
- Edit, delete
Driver detail /delivery/drivers/[id]
- Profile tab
- Lifecycle tab + actions (activate, suspend, …)
- Credentials tab (read)
- Documents tab (read)
- Timeline from lifecycle API
Integrations
- External providers CRUD
- Routing engines CRUD
Admin
- Settings upsert
- Audit search
- Permissions catalog
- Health status
- Capabilities grid
Phase-gated screens (checklist when backend enables)
When features.<name> becomes true in /capabilities:
- Replace phase gate with real implementation
- Connect WebSocket for tracking/dispatch
- Integrate shared map component
- Add realtime polling fallback
Dashboard checklist
- Executive: real org/hub/driver counts
- Dispatcher: dispatch queue metrics (10.5)
- Live ops: tracking sessions (10.7)
- Fleet: vehicle counts (10.2)
Validation loop
npm run validate:delivery
npm run build
Review delivery-validation-report.md after each backend phase upgrade.