Creates account
Chooses privacy defaults and confirms age eligibility. Continue with Apple authenticates only.
From first meal to better week.
Solid cards are actions. Dashed cards are decisions. The coloured top rule marks a trust-sensitive checkpoint.
Onboarding to Today
Set a credible starting point, then hand off to the real home screen.
SuccessA confirmed starting point and direct arrival on Today.
Fills body data
Enter editable fields manually or choose the optional Apple Health assist.
Reviews health permission
The requested body and activity categories are explained before the separate system permission.
Confirms available data
Imported height and weight stay editable. Missing fields and private equation sex are entered manually.
Selects goal
Lose, maintain, gain, or recomposition. Unsafe rates are unavailable.
Sets destination
Chooses a landing weight for Lose, Maintain, or Gain; Recomposition uses an optional body-fat percentage with a comparable measurement source.
Prefills activity context
Available recent steps and workouts suggest a category that the person confirms or edits; otherwise use the manual questions.
Confirms target
Sees the basis and can choose a manual target.
Acknowledges setup
Eligible and manual-only paths preserve their source context. Each shows exactly one CTA: Go to Today.
Arrives on Today
Food logging is available as a primary home-screen action, outside onboarding.
Trust checkpointSign in with Apple and Apple Health permission remain separate. Never imply access is automatic or complete; confirm imported values, keep manual fallback visible, and never source private equation sex silently. Explain target basis and keep manual override visible. If the safety screen blocks automation, use a manual-target-only path and do not show an automated maintenance estimate. Acknowledgement leads directly to Today; do not insert a food-logging decision into onboarding.
Commercial boundaryNo paywall. Activation and the daily tracker are free.
Repeat a usual meal
The primary memory-first path for recurring food.
SuccessA familiar meal is logged in two taps or under ten seconds.
Surfaces likely meal
Based on time, day, and the person’s own history—not a public guess.
Repeat as usual?
One tap repeats. Edit opens portion and ingredient controls.
Adjusts if needed
Change amount, remove an item, or save this as a new variation.
Logs with source
The new Food Log Events point back to the Meal Template version used.
Updates Today and Food
Today refreshes calories, protein, and next action; Food preserves the itemized daily record.
Trust checkpointRepeating a meal creates a log event; it never rewrites the historical object.
Commercial boundaryCore reuse stays free. The confirmed Premium features are AI photo recognition and the private Photo Journal.
Exact search or barcode
When exact data exists, prediction should get out of the way.
SuccessThe person can identify the source, unit, and serving basis before saving.
Search or scan?
Both inputs remain prominent on the add-food surface.
Ranks credible matches
Personal history first, then verified regional data, then public entries.
Checks source and unit
Gram, serving, barcode, and provenance are visible.
Correct or continue?
A local correction can be saved without corrupting the public source.
Sets amount
Weight and common portions remain interchangeable.
Adds to meal
The item becomes a Food Log Event. The person can later group events or save a reusable Meal Template.
Trust checkpointNever hide provenance or silently prefer a duplicate with weaker data.
Commercial boundarySearch and barcode stay free; competitors create resentment when these are gated.
Voice-assisted draft
Speed without pretending that spoken portions are exact.
SuccessA reviewable draft becomes a confirmed log with uncertainty resolved.
Describes the meal
“Chicken wrap with cheese and a small latte.”
Builds a draft
Matches items from personal memory and credible food sources.
Marks uncertainty
Low-confidence food or portion estimates are visually distinct.
Material difference?
If the estimate can materially change calories or protein, confirmation is required.
Edits or confirms
Uses natural units, grams, or a remembered portion.
Saves the confirmed log
Only confirmed values enter weekly analysis.
Trust checkpointDrafts never count as complete-day evidence until confirmed.
Commercial boundaryVoice drafts remain part of core logging. The confirmed Premium boundary applies to AI photo recognition and the private Photo Journal.
Shared prepared meal
Create once, then let each person log the amount on their own plate.
SuccessTwo private logs point to one shared recipe without overwriting each other.
Creates the recipe
Adds ingredients and records final prepared weight.
Shares Meal Template
Sends a private link to a partner.
Accept this meal?
Sees ingredients and nutrition source, not the cook’s targets or diary.
Logs own portion
350 g and 500 g can come from the same prepared batch.
Creates private events
Each log belongs to its person; the shared object remains intact.
Reuses next time
Update the new batch or repeat the previous version.
Trust checkpointSharing never reveals weight, goals, other meals, or recommendation history.
Commercial boundaryCore meal sharing remains free. The $49 annual Duo plan grants Premium to two linked accounts without merging their private records.
Validate the week, then decide
The weekly value loop and the product’s most important integrity safeguard.
SuccessOne explainable recommendation uses only days the person has validated.
Closes and celebrates the week
Separates supported goal outcomes from controllable behaviours such as validated logging, protein coverage, steps against personal intent, and training consistency.
Flags suspicious days
Missing dinner, unusually low intake, or unconfirmed drafts become review items.
Reviews each day
Confirms intake completeness separately from any corrections or review status.
Recalculates evidence
Shows exactly which days and measurements remain in the analysis.
Explains the longer trend
The calendar week remains context. Eligible calibration uses the approved rolling evidence window and separates observation, exclusion, interpretation, and confidence.
Adds next-week context
Types or speaks optional constraints, then confirms the editable transcript and every structured label before use.
Offers one plan decision
Keep, adjust, collect more evidence, flexible week, or manual-only review is explained with exact values and dates.
Accepts, keeps, edits, defers, or rejects
No target changes before acceptance. The final decision remains inspectable and undoable.
Trust checkpointNo target changes silently. Voice is an input method, not an instruction channel. Weak weeks can result in “keep collecting data.”
Commercial boundaryWeekly check-in, validated recommendations, and decision history remain in the free core.
Review Journal and plan
Connect weekly progress, measures, check-ins, and plan evidence without overstating causality.
SuccessThe person understands the trajectory, can start a check-in, and can inspect or change the current plan deliberately.
Opens a week
Reviews averages, totals, coverage, and the accepted plan decision.
Offers weekly check-in
Completed weeks enter validation before any recommendation is generated.
Reviews measures
Weight and compatible body measurements remain available; private progress photos are marked Premium.
Reviews current plan
Inspects baseline inputs, sources, target origin, formula version, and decision history.
Continue, start, or reset?
Keep the plan, archive it and confirm a new goal, destination, and baseline, or reset recommendation calibration through a separate warning flow.
Preserves history
New-plan and reset actions retain food, measures, photos, check-ins, prior plans, and manual-only safety eligibility.
Trust checkpointPhotos are private by default; reset is not data deletion; correlation language remains explicit.
Commercial boundaryMeasurement tracking remains available; progress photos are Premium. Other Journal intelligence boundaries remain open.
Control the app and the record
Settings makes account state, permissions, assistance, entitlement, and data ownership explicit.
SuccessThe person can change how the app behaves and manage their data without entering a plan or diary workflow.
Shows current state
Account source, units, Health access, notifications, assistance, and entitlement appear on the overview.
Sets units and region
Display changes preserve source values, precision, provenance, and history.
Reviews Apple Health
Category-specific access, last sync, attribution, disconnect, and manual fallback remain visible.
Controls assistance
Notification, visibility, insight, recommendation, and food-personalization controls remain independent.
Reviews entitlement
Free, Individual Premium, and Duo state use the confirmed prices and privacy boundary.
Imports previous history
A CSV is selected, mapped, interpreted, and previewed before any attributed record is written. Imported days remain Unreviewed until reconciled.
Exports or deletes
Portable import and export stay free; record and account deletion use explicit, protected flows.
Trust checkpointContinue with Apple is not Health permission; disconnect is not deletion; CSV import never overwrites silently; algorithm reset stays in Journal.
Commercial boundaryCore controls, import, export, and deletion remain free. Premium owns only its confirmed visual-assistance features.
Review the storyboard.
The neutral wireframes sit with the flows they implement. They keep product structure distinct from the Organic site language while making the confirmed architecture reviewable.
A
Onboarding to Today.
Apple Health consent, editable body data, manual-only safety, four goals and destinations, target review, setup acknowledgement, and the handoff to Today.
B
Today, Food, and Journal.
Daily consumption, weekly context, direct logging, unified food entry, reconciled diaries, weekly progress, plan management, and Premium photo moments.
Empty states explain what to log and why. They never manufacture an insight.
Drafts, suspicious days, and weak sources remain visibly unresolved.
“Keep the plan” is a valid recommendation when confidence is low.