Decision: navigation model (2 tabs, Home labelled “Log”) #8
Labels
No labels
bug
chore
feature
spike
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Blocks
#13 Scaffold Android app (Kotlin + Compose)
utilities/Logbook
#15 Navigation scaffold: 2-tab nav + slide-over sheet host
utilities/Logbook
Reference
utilities/Logbook#8
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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:
✎) — the home surface, labelled "Log", not "Home",☰),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).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.