From the developer of Repeat Eat
A food journal built for meals that repeat
Personal notes about building a quicker, calmer way to keep track of food without turning every meal into a data-entry task.
Why I built Repeat Eat
A health wake-up call, a swimming habit, and the frustration that led me to build my own food journal.
Read moreFood logging should remember what you eat
Most meals are variations of familiar meals. A useful journal should be designed around that fact.
Read moreWhy Repeat Eat is a one-time purchase
A food journal should feel like a tool you own, with local data, portable exports, and no recurring fee.
Read moreWhy Repeat Eat works with your AI
Why AI stays optional, what BYOAI means, and why meals move through an open, reviewable format.
Read moreA less obvious benefit of external AI
How a focused daily journal can support a broader nutritional review once a month or every few months.
Read moreYour food history should not be the price of switching apps
How AI makes closed data less durable as a way to retain people, and why useful products do not need that barrier.
Read moreQuestions or suggestions?
For questions about the app, bug reports, or suggestions, email repeateat.support@gmail.com.