Decision: navigation model (2 tabs, Home labelled “Log”) #8

Closed
opened 2026-07-23 14:46:24 +02:00 by cloudbot · 1 comment
Collaborator

Decision — confirm the navigation model before the navigation scaffold is built.

There's a discrepancy between the design doc and the prototype that needs resolving:

  • Design doc §2 describes a three-tab bottom nav with the home surface labelled "Home" (Home / Stream / implicit Template Sheet).
  • The committed prototype and design-system skill describe two bottom-nav tabs:
    • Log (glyph ) — the home surface, labelled "Log", not "Home",
    • Stream (glyph ),
    • and the entry/person editor is not a tab — it's a full-screen surface that slides in from the right over the whole app.

The design reference states the prototype wins when it and a spec disagree.

What to decide

Confirm the two-tab model (Log + Stream) with the editor as a slide-over surface, and the "Log" label for the home tab — superseding the doc's three-tab/"Home" description.

Blocks: the navigation scaffold (M1).

Recommendation: adopt the prototype's two-tab "Log" + "Stream" model. The "third tab" in the doc was always the modal sheet, which isn't a real tab; the prototype's slide-over is the cleaner expression of the same idea. Worth updating design doc §2 to match so the two sources stop disagreeing.

Source: Solution Design — Family App v1 §2 (doc vpBNbG4TsV); prototype design/Family App.dc.html; skills/design-system/SKILL.md (Navigation).

**Decision — confirm the navigation model before the navigation scaffold is built.** There's a **discrepancy between the design doc and the prototype** that needs resolving: - **Design doc §2** describes a **three-tab** bottom nav with the home surface labelled **"Home"** (Home / Stream / implicit Template Sheet). - **The committed prototype and design-system skill** describe **two** bottom-nav tabs: - **Log** (glyph `✎`) — the home surface, labelled **"Log", not "Home"**, - **Stream** (glyph `☰`), - and the entry/person editor is **not a tab** — it's a full-screen surface that slides in from the right over the whole app. The design reference states the prototype wins when it and a spec disagree. ### What to decide Confirm the **two-tab model (Log + Stream)** with the editor as a slide-over surface, and the **"Log"** label for the home tab — superseding the doc's three-tab/"Home" description. **Blocks:** the navigation scaffold (M1). **Recommendation:** adopt the prototype's two-tab "Log" + "Stream" model. The "third tab" in the doc was always the modal sheet, which isn't a real tab; the prototype's slide-over is the cleaner expression of the same idea. Worth updating design doc §2 to match so the two sources stop disagreeing. **Source:** Solution Design — Family App v1 §2 ([doc vpBNbG4TsV](https://outline.marquezkeenan.family/doc/solution-design-family-app-v1-vpBNbG4TsV)); prototype `design/Family App.dc.html`; `skills/design-system/SKILL.md` (Navigation).
Owner

Prototype wins on UX - two tabs on the bottom. Row of person notes at the top of Home, and a scrollable grid of Create buttons below, defined by templates in Outline.

Prototype wins on UX - two tabs on the bottom. Row of person notes at the top of Home, and a scrollable grid of Create buttons below, defined by templates in Outline.
ben closed this issue 2026-07-23 17:42:18 +02:00
Sign in to join this conversation.
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
utilities/Logbook#8
No description provided.