Overview
Build a role-based dashboard activity feed for investors, drivers, and admins.
Problem
ChainMove users need a clear place to see recent platform activity such as wallet updates, repayment updates, KYC status changes, investment confirmations, vehicle assignments, payout updates, and Stellar-related updates.
Expected solution
Create an activity feed module with:
- role-specific feed items
- read and unread state
- activity categories
- timeline UI component
- feed item links to relevant dashboard pages
- empty, loading, and error states
- optional unread count in the dashboard header
Example feed items
- Wallet funding completed
- Investment confirmed
- Driver repayment received
- KYC status updated
- Vehicle assigned
- Payout processed
- Stellar activity indexed
Backend considerations
Use existing user notification fields where available or introduce a simple activity model/service if needed. Keep feed generation reusable and avoid hardcoding all activity in UI components.
Files likely involved
- dashboard header components
- activity feed components
- user or activity model
- activity API routes
- dashboard pages
Acceptance criteria
- Users can view a role-specific activity feed.
- Feed items support read/unread state.
- Multiple activity categories are supported.
- Header unread count works where applicable.
- Empty/loading/error states are implemented.
npm run lint and npm run build pass.
Suggested labels
dashboard, activity-feed, frontend, backend, hard
Difficulty
Hard
Overview
Build a role-based dashboard activity feed for investors, drivers, and admins.
Problem
ChainMove users need a clear place to see recent platform activity such as wallet updates, repayment updates, KYC status changes, investment confirmations, vehicle assignments, payout updates, and Stellar-related updates.
Expected solution
Create an activity feed module with:
Example feed items
Backend considerations
Use existing user notification fields where available or introduce a simple activity model/service if needed. Keep feed generation reusable and avoid hardcoding all activity in UI components.
Files likely involved
Acceptance criteria
npm run lintandnpm run buildpass.Suggested labels
dashboard,activity-feed,frontend,backend,hardDifficulty
Hard