A daily record that asks less of the day.
I wanted to keep track of food, gym sessions, and daily activity without making every meal an administrative exercise. Searching for a food, choosing a serving, checking the values, and saving an entry can seem minor once. Repeated throughout a week, that effort begins to dominate the habit.
Food Tracker began as personal automation. The aim was a useful record I could live with, rather than a more elaborate logging screen. An ordinary sentence such as “I ate two eggs” offered a simpler starting point than asking me to translate the meal into a form first.
The tool takes natural-language input, parses the food or activity, and turns it into structured entries. Food entries are broken into nutritional values automatically, while gym and daily activity belong to the same continuing record. Summaries make that record easier to review without repeating the original entry work.
The interface should make the habit easier to keep. Explore sample entries to see how plain language can become an organised activity record.
“Oats, a banana, and coffee before work.”
Prepared examples of the intended interaction. No live AI processing.
Enter food or an activity in ordinary language, close to when it happens. The interaction starts with what is easy to remember: a meal, a gym session, or another daily activity. It avoids making category selection the first task.
The system converts the description into nutritional or activity data and logs the result. This is where the automation carries work that a conventional form pushes onto the user, connecting natural input to a record that can be compared over time.
Look at daily or weekly summaries to understand the accumulated record. Food, gym, and activity sit within a broader view of the day. The purpose of collecting them is to make review easier, rather than simply increasing the amount of stored data.
A short description is the primary input. This makes the user’s familiar expression the starting point and puts the translation into structured fields inside the system, where it can happen without repeated navigation.
Gym sessions and daily activity belong beside food logging because the personal question concerns an overall routine. Treating those records together gives summaries a more useful purpose than isolated lists of meals or workouts.
A tracking flow must work repeatedly, on ordinary days. The design priority is sustained low effort. Repeated meals, understandable output, and easy correction are important considerations when deciding whether automation is actually reducing the burden.
Food Tracker is a personal tool rather than a published health service. Its automated breakdown depends on the information supplied and how the entry is interpreted. The project describes logging and review; it makes no claim about nutritional precision, health outcomes, or medical recommendations.
What should happen when a portion is unclear or a meal contains several ingredients? How could someone correct one assumption without rewriting the whole entry? A next exploration would ask how to make uncertainty and corrections visible while preserving the ease of the original interaction.
Better responses start with better context.