We have streamsApi.analytics() defined in the API service but it's never called anywhere. The backend already has working endpoints — /api/analytics/stats, /api/analytics/earnings/:address, /api/analytics/balance/:address. They're just sitting there unused.
Build an /analytics page that actually uses them. Summary cards at the top (total streams, active count, total streamed, monthly burn rate) and then charts below — streamed over time, token distribution breakdown, active vs cancelled vs completed. Use recharts or something lightweight, don't need anything fancy.
Should also show earnings broken down by token and a table of historical stream data. Wire it all up to the existing API endpoints. Refresh data when the wallet connects or disconnects.
Done when:
- Summary cards pull real data from the API
- At least 3 different charts rendering
- Data refreshes on wallet state change
- Empty state when there's no streams yet
- Responsive on mobile
- Loading skeletons while fetching
We have
streamsApi.analytics()defined in the API service but it's never called anywhere. The backend already has working endpoints —/api/analytics/stats,/api/analytics/earnings/:address,/api/analytics/balance/:address. They're just sitting there unused.Build an
/analyticspage that actually uses them. Summary cards at the top (total streams, active count, total streamed, monthly burn rate) and then charts below — streamed over time, token distribution breakdown, active vs cancelled vs completed. Use recharts or something lightweight, don't need anything fancy.Should also show earnings broken down by token and a table of historical stream data. Wire it all up to the existing API endpoints. Refresh data when the wallet connects or disconnects.
Done when: