Skip to main content

Dashboards — feature architecture

DRAFT — design under review. A new top-level nav surface: a widget-based dashboard that aggregates the family's at-a-glance state (budget, goals, today, members). It is also the source of the lean-back home screen for the TV + desktop home app (the BYO-screen family display).

Two modes from one surface​

  • Lean-forward (phone/tablet, in-app tab): an interactive Dashboards tab — widgets you tap to drill into the underlying surface (a goal widget → Member Profile; the budget widget → recommend/edit).
  • Lean-back (TV / desktop home app): the same widgets composed into an ambient family display — large, glanceable, low-interaction (the BYO-screen / family-display concept; see the kiosk / family-display decision + the market analysis §12 hardware-vs-software wedge).

One Dashboard config drives both; the lean-back home is a layout/skin of the same widgets.

Widgets (initial)​

  1. Family budget (the first widget) — moved here from the Household tab. Household budget + summary; role-aware (non-admin → recommend; admin → edit link) per Money & Envelopes + Household.
  2. Goal summaries — family + per-member goal progress.
  3. Today — at-a-glance chores / approvals state.
  4. Member glance — per-member wallet/goal chips (→ Member Profile).

(Widget set + ordering become configurable later; the ambient layout is a TV/desktop skin of the same widgets.)

On phone, adds a primary tab: Home (Today) · Dashboards · Catalog · Household · Profile.

On desktop + TV it is a single view — not two joined panes but one unified lean-back home: the act surface (Today) and the glance widgets (Dashboards) compose into a single screen, so the family sees "what to do now" and "how we're doing" at once. Today + Dashboards are the same view, laid out together. On phone, limited screen real estate splits them into separate tabs. (Open: whether this single view is the default landing on desktop/TV.)

Platform & data​

  • The lean-back home (TV + desktop home app) renders these widgets as an ambient display — the BYO-screen / family-display product direction.
  • Pulls the budget + summaries off the Household tab (which becomes the people surface: member tiles + family goals) — see Household.
  • Mostly read-only aggregation over existing SDK surfaces (members, wallet/envelopes, goals, budget) — little new domain, mostly new presentation. A watch*-stream story keeps the ambient display live.

Open decisions​

  • Widget set + ordering (and whether users customize it).
  • Default landing per platform (phone = Today; TV/desktop = Dashboards?).
  • Lean-back vs lean-forward: same widgets at different density/interaction, or distinct layouts?