meal

Summary

A meal already logged, and editable.

Raw wireframe

• .context/designs/mobile/food/meal.html

Why it is drawn this way

The missing level. Tapping a meal on Today went straight to a single component, skipping the meal itself.

Deliberately not the same screen as the scan result. That one is a decision — log it or improve it. This one is a record: already logged, already counted, and editable. Same component rows, different verbs.

Two taps, two questions. The slot chip opens the meal picker; the date line opens the when-sheet. They are separate because a meal eaten at the wrong hour is a different mistake from one filed on the wrong day, and one control doing both would have to ask twice anyway.

The still-open question appears only when a component is low confidence.

The cooking-fat card is conditional, and the condition is the point. It offers to ADD a fat only when the plate has no fat row; with one, the row says the same thing and the card would be the duplicate this screen forbids. The wireframe draws the plate that HAS a fat row, so the card itself lives in fat-card rather than in a second copy of this frame.

A fat row opens fat, never the portion editor. Oil is a judgement with named answers, not a food to weigh — see portion.

Related

• confidence
• portion
• fat
• fat-card

Sources

• .context/designs/mobile/food/meal.html