Summary
Build the actual dashboard the README promises, consuming the authenticated API once it exists.
Description
Implement the WhatsApp-initiated login flow client-side (request code/link, exchange for session, persist session appropriately).
Build balance and transaction-history views under apps/frontend/src/app/, using the typed API client, the loading/error/empty state primitives, and the AddressChip component from earlier issues.
Build the export-to-self-custody UI, calling into the backend's export flow equivalent for the web (or guiding the user to do it via WhatsApp if web-initiated export is out of scope for MVP — decide explicitly and document the choice).
Add tests for the key views (rendering with mocked API responses for loading/empty/populated/error states).
Deliverables
- Login, balances, history, and export views
- Wired to the dashboard API
- Tests for each view's states
Dependencies
Summary
Build the actual dashboard the README promises, consuming the authenticated API once it exists.
Description
Implement the WhatsApp-initiated login flow client-side (request code/link, exchange for session, persist session appropriately).
Build balance and transaction-history views under
apps/frontend/src/app/, using the typed API client, the loading/error/empty state primitives, and theAddressChipcomponent from earlier issues.Build the export-to-self-custody UI, calling into the backend's
exportflow equivalent for the web (or guiding the user to do it via WhatsApp if web-initiated export is out of scope for MVP — decide explicitly and document the choice).Add tests for the key views (rendering with mocked API responses for loading/empty/populated/error states).
Deliverables
Dependencies