Repository navigation
[Feature] Fast journal and meal/activity logging #94
Description
Outcome
Let users add the context that makes glucose understandable: meals, activity, notes, and lightweight subjective tags, fully offline and in seconds.
Dependencies
- Production persistence depends on [Feature] Source-aware health data spine and import identity #89.
- Final chart overlay integration belongs to the unified body-timeline issue.
- Build against the existing
HealthEventand repository abstractions rather than introducing UI-only models.
Scope
- Quick add: meal, activity/workout, and note.
- Optional tags: caffeine, alcohol, stress, illness, fasting, sleep quality, mood, and energy.
- Extend meals with fiber, stable title/category, serving/template metadata, and optional macros.
- Recent meals, templates, and duplicate previous.
- Timeline browse, filter, edit, delete, and undo where safe.
- Tap a timestamp to prefill an event.
- Clear source/provenance distinction between manual and imported context.
- App Intents/voice/photo capture remain later accelerators; manual workflow is authoritative.
Parallelization
Form and interaction design can begin using an injected in-memory repository while #89 lands. Coordinate repository contracts with #89 and shared navigation components with #91. Do not concurrently edit the final glucose chart.
Acceptance criteria
- A basic meal can be saved in under 10 seconds and no more than three taps after Quick Add opens.
- Meal, activity, and note create/edit/delete persist across relaunch.
- Duplicate and templates preserve intended fields without copying timestamps or private identifiers incorrectly.
- Fiber and optional macro fields round-trip through storage/export.
- Timeline clearly distinguishes manual events from imported samples.
- Works fully offline and with AI disabled.
- Empty, error, keyboard, Dynamic Type, screen-reader, and timezone cases are tested.
- No medical, nutritional-treatment, dosing, or causal advice appears.
Out of scope
- Food database.
- AI/photo macro guessing.
- Meal-response conclusions.
- Final combined chart rendering.
Repository-owner recreation of the legacy issue at #41. The original discussion remains available there.
Activity
shroominic commentedon Sep 1, 2026
Participant feedback: daily diary
A participant reported that a handwritten notebook containing every meal and food item was useful during review. This validates the core daily notebook use case in this issue, especially for people who do not already track every meal.
Acceptance additions from the interview:
The proactive, opt-in reminder flow is tracked separately in #103.
feat(journal): add local fast diary (partial #94) (#73)