fat

Summary

The one component a photograph can never show.

Raw wireframe

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

Why it is drawn this way

A screen of its own, reachable in one tap. Until this screen existed, cooking fat was only reachable if the model happened to ask about it. That is backwards: it is the largest hidden number on most plates in this market, the user always knows the answer, and it should be one tap from the meal whether or not the estimator thought to ask.

Every route to a fat row lands here, not on the portion editor. A fat row is the one component whose quantity is not a measurement, so the generic editor has no fat face — see portion. Callers branch on isFatComponent.

Which fat, then how much. It names the thing before it measures it, and that is where "None at all" honestly belongs.

The live total is pinned at the top, so every tap below has a visible effect. A picker whose consequence is two screens away is a picker people stop trusting.

It was cut to one screen, and what went was prose. It ran to about a screen and a half, and the amount — the question that actually moves the number — was the half below the fold. The four fats were four full-width rows carrying a line of prose each, explaining constants that the rows below already print as "+124 kcal"; they are a 2x2 grid now. The three-line note about the oils being interchangeable is one line. "Log this dish again and it starts from your answer" described something that happens next time, on a screen whose job is this time. The "camera can't see this" chip moved onto the total card, where it costs no row of its own.

Related

• the-ask
• confidence
• portion

Sources

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