[Idea] Show overall stats in the home page

[Commit25uccess]

Affected area

Budgets and statistics

Problem or opportunity

We already have stats in each individual groups/friends.
So, an aggregated stats on the homepage would be better and would make the homepage much nicer instead of just listing groups and friends. That would also allow users to know the overall expenses/income. We can add filter as needed.

Desired outcome

An aggregated stats on the homepage with filters allowing users to view their or their friends aggregated income/expenses

Alternatives or workarounds

Individual groups/friends stats

Additional context

No response

Before submitting

• I searched existing issues for similar ideas.
• I removed personal, financial, and secret information from this public proposal.

[pullfrog]

Analysis & plan for issue #87 — "Show overall stats in the home page"

Assessment

Actionable. The home page already has a cross-group net-balance roll-up (the "Across groups" card, fed by trpc.overview.get → stats.balanceSummaries / stats.peopleBalances), and each group has a full stats dashboard (/groups/:id/stats → trpc.groups.stats.get). What is missing is the aggregation the issue asks for: overall spending/income stats across all of a user's ledgers (groups + friends), with filters, on the home page. The plumbing to build it largely exists.

Recommended design

• New tRPC procedure overview.stats.get, mirroring groups.stats.get: input { period, scope, customRange? }, output per-currency aggregated stats. Reuse the existing overviewExpenseSelect / toBalanceExpense loaders (already in apps/api/src/trpc/routers/overview/index.ts) and the domain totals (getTotalGroupSpending, getTotalActiveUserPaidFor, getTotalActiveUserShare) or buildGroupStatsDashboard per ledger, aggregated by currency.
• Scope filter All / Groups / Friends (filter on Group.groupType) — directly matches the issue's "their or their friends aggregated income/expenses".
• Currency handling: aggregate per currency (same convention as balanceSummaries). No cross-currency FX conversion in the MVP — a single "overall" number across ledgers in different currencies would be misleading; conversion to the account default currency is a clean follow-up given the existing server-authoritative rate machinery.
• "Income/expenses" semantics: the app has no income concept; map to the existing totals — total spending, "you spent" (getTotalActiveUserPaidFor), "your share" (getTotalActiveUserShare). Net owed/owe is already covered by the existing card.
• UI: a stats section on the home page above the group list reusing SummaryCard, StatsPeriodPicker, Money, and the existing loading/offline/error patterns from StatsDashboard.

Milestones

1. API — overview.stats.get procedure + zod output schema (outputs/overview-stats.ts); unit tests with createCaller + prisma mock, following the patterns in apps/api/src/trpc/routers/overview/index.test.ts.
2. Web — OverallStats section on the home page (apps/web/src/app/groups/recent-group-list.tsx area): scope toggle + period picker + per-currency summary cards (total spent / you spent / your share / expense count), with keepPreviousData and consistent empty/error/offline states.
3. i18n — add strings via bun i18n (en-US first, then dispatch — never hand-edit apps/web/src/messages/*).
4. Verification — bun run check (formatting/lint/typecheck) + targeted vitest for the new router.

Open questions to confirm before implementation

1. Currency: per-currency cards (recommended for MVP) vs converting everything to the account's default currency?
2. "Income": confirm the mapping to "you spent" / "your share" (net balance already shown).
3. Archived groups: exclude from aggregated stats (recommended) — the current balance card counts active memberships regardless of archive state.
4. Placement/UX: new section vs a third tab in the existing "Across groups" card.

No code changes yet — plan only, per the issue being a feature idea.

Task list (4/4 completed)

• Fetch issue [Idea] Show overall stats in the home page #87 details and comments
• Understand home page architecture and existing stats/analytics
• Assess feasibility and identify ambiguities
• Produce actionable plan and report progress

  ^{｜ Implement plan ➔ ｜ View workflow run ｜ via Pullfrog ｜ Using openai-compatible/deepseek-v4-flash-free ｜ 𝕏}