Accounts command center
Primary account tab with Connect, Refresh, Add institution, balance groups, freshness badges, and partial-error cards.
PLAID READ-ONLYNORMAL USER COMMANDSNO LIVE PLAID CALLS
Plaid mockups as real app usage flows.
This prototype shows what users should actually do inside Helm: tap commands, ask normal questions, inspect account data, filter history, chart trends, and recover from connection problems. Each flow names the UI we need to build and the safe backend action behind it.
Normal commands users should be able to make.
Tap each command to see the exact app screen, user action, backend call, and states we need to support.
State coverage we must design
Before linkingShow one primary CTA: Connect account with Plaid. Do not show fake balances.
Linked + freshShow account data, freshness, institution count, and read-only mode.
Blocked/staleShow exact issue: re-link, OAuth redirect, item error, or partial institution failure.
What this tells us to create.
These are the concrete app capabilities implied by the user actions above.
Natural command chips
Tap actions like “Show my last 90 days,” “Find recurring bills,” “Compare this month,” and “Explain this spike.”
History explorer
Transaction list with date/category/merchant filters, drilldowns from charts, saved insights, and export/share surfaces.
Chart surfaces
Cashflow line chart, spend category bars, merchant leaderboard, net-worth/balance trend, and investment activity timeline.
Safe Plaid backend
Server-owned Plaid secrets/tokens, link-token creation, public-token exchange, aggregated read endpoints, and no token returned to phone.
Honest error UX
LIVE_UNLINKED, STALE_DATA, PARTIAL_ITEM_ERROR, OAuth redirect warning, institution action required, and no fabricated data.
Showcase only: This is a static app-usage prototype. It does not open Plaid Link, call Plaid APIs, contain client secrets/access tokens, move money, or connect to broker actions.