Food logging should remember what you eat

Breakfasts repeat. Lunches repeat. Dinners repeat. Even when a meal changes, the difference is often small: one egg instead of two, a different fruit, half a drink, or a larger portion of one item.

A food journal should make those small changes easy. It should not ask you to search a huge database and rebuild the entire meal every time.

Repeat first, then adjust

Repeat Eat starts with meals and dishes you already know. You can reuse a familiar meal and change only what was different today.

• If you did not finish something, reduce or remove that item.
• If you ate a little more, increase that item without changing the rest of the meal.
• If a meal is completely new, add it once and it becomes familiar next time.

In my own use, a familiar meal takes around 10 to 20 seconds to record. A completely new meal usually takes up to two minutes, and often less.

Useful estimates beat perfect data entry

The goal is not laboratory precision. The goal is a journal you can keep using long enough to understand your habits. Approximate calories, protein, and fibre can still answer useful questions: What have I eaten today? Am I probably in a deficit? Am I getting enough protein?

AI can help identify a meal or suggest estimates, but it stays optional. Every result should be reviewable and editable before it becomes part of the journal.