Nutrition

What this chapter is for

The nutrition screen is a day, not a diary. It always shows exactly one calendar day with everything you ate and holds it against your targets. Anything that spans several days lives on the dashboard.

The day

The date sits at the top. Swipe left and right to move between days, and one tap brings you back to today. Below it is the balance: the day’s calories plus protein, carbs and fat, each against your target.

The meals are listed underneath in the order you entered them. Each one is stamped with a time — the time of entry. You open an entry with a tap; there you change it, and there you delete it as well. If you log your lunch in the evening, correct the time on the entry. This is not cosmetics: from those times the dashboard later works out your rhythm — when you eat your first meal, how long the gaps are, how your meals sit around training.

Planned and eaten

An entry can be one of two things: eaten or planned. Planned items do not count towards the day’s balance yet; they sit in their own section with their own total. That way you can work out in the morning whether the day still adds up with the dinner you have in mind — the app tells you when the plan takes you past your daily target. Later you tick the planned entry off as eaten instead of entering it again.

Logging something

There are three ways to record a food:

Way	What for
Search	Everything you have logged before, plus the bundled foods
Scan a barcode	Packaged products
Enter manually	Home cooking and everything without a barcode

For a manual entry the app asks for everything: name, calories, protein, carbohydrates, fat and amount (a typed 0 counts). That way no half-finished food ends up in your list. A hint appears only when you leave a field, not while you are typing.

Entry of your own food with a name field and the values per 100 grams — Your own food needs a name and all values per 100 grams.

Whichever way you take, you finish by giving the amount — in millilitres for a drink, in grams for anything else. Which of the two applies is decided by the food and not by you: a cola is poured, a steak is weighed, and 100 ml of oil weigh 92 g. When you scan a product, the app takes that straight from it.

Every nutrition value refers to 100 g or 100 ml respectively; the amount scales it down or up.

Even if you switched to pounds and feet under Options, amounts and nutrition values for food stay in grams and millilitres — just as every label gives them. The units apply to training weights and body measurements.

The barcode scan

The scan looks on your device first. If the app does not know the product, it asks Open Food Facts — sending the barcode number along with, for technical reasons, your IP address and an app identifier. Camera images and your entries never leave the device. The app only accepts the answer if it belongs to the barcode you scanned; if the service reports a different product, it counts as not found. The product it finds is stored locally and is there instantly next time, offline included.

Two cases need you:

Nobody knows the product. Then you create it yourself — typed once, stored for good.
The figures are wrong. Then correct them. Your corrected values take precedence. Should Open Food Facts learn about the product later, the app asks whether to replace your values with the new ones — it never does so on its own.

Where the figures come from. The Open Food Facts data is collected by a community; it is published under the Open Database License (ODbL) and is not verified by us. So compare it with the package. If Open Food Facts does not state a value, the app shows a question mark instead of a number — it does not invent a zero. In the day’s total a missing value counts as 0, and the app tells you that the total is incomplete. Your own values stay on your device and replace the database’s.

Allergens and ingredients are not shown in the app. If you have allergies or intolerances, only the package counts.

If Open Food Facts cannot be reached, the app tells you so and lets you create the food yourself. It does not ask again on its own.

A food of your own gets one name, in the language you are using the app in at that moment.

Recipes

What you eat often, you create once as a recipe: with ingredients and amounts and, if you like, a short preparation. The app adds up the nutrition values. When you log a meal you take the recipe with its amounts and adjust them if today was different. If you changed amounts, the app asks exactly once whether that applies to this meal only or whether the recipe should stay that way from now on. It discards a recipe you have started only after asking.

Question “Recipe adjusted” after an amount was changed, with two ways to save — If an amount was changed, the app asks whether the change applies to this meal only or to the recipe.

Your targets

You set the targets yourself, and there are three ways to get there:

By hand. Enter calories and the three macronutrients, done.
From your profile. The app estimates your daily need with the Mifflin-St Jeor formula from age, height, weight, gender and daily activity. One tap adopts the value. It remains an estimate — a calculation, not a measurement.
Via grams per kilogram of body weight. You pick a pattern as your starting point — muscle gain, fat loss or maintenance — and the app converts the factors against your current weight into grams.

The third way has a property that saves you work: when your weight changes, the targets change with it. Log a new weight under Body and the macro targets are recalculated without you opening the targets screen again. Without a stored weight this way does not work — you are then left with the factors and no gram totals.

On top of that you set a macro focus: the nutrient that matters most to you. It decides what gets emphasised on the daily screen.

flowchart LR
  Profile["Profile: age, height, gender, activity"] --> TDEE["Estimated daily need"]
  TDEE --> Targets["Daily targets"]
  Body["Body: current weight"] --> PerKg["Grams per kilogram"]
  PerKg --> Targets
  Manual["Your own input"] --> Targets
  Targets --> Day["Daily balance"]
  Meals["Logged meals"] --> Day

The targets have three sources, but only one applies: the one saved last.

When something does not work

The scanner does not open. Camera permission is missing. You can grant it in your phone’s system settings.
The product is not found. Open Food Facts is an open database; not every product is in it, and regional goods often are not. Create it once yourself — after that your app knows it.
The nutrition facts look wrong. They come out of the database exactly as somebody entered them there. Correct them on the product; the correction sticks.
The day is empty although you logged something. The date at the top is probably on another day. Jumping back to today is one tap.

How it fits together

The profile supplies the need estimate, Body the weight for the grams-per-kilogram calculation, and the dashboard gathers the days into weeks, months and years.