About the Founder
Built because food logging shouldn't be a chore
I spent years fighting with nutrition apps that made food logging feel like homework. Then I built a Telegram bot where I could just describe what I ate and let AI handle the rest. The friction disappeared, and I actually stuck with it. That bot became BiteBot.
I'm Aaron — a solo developer building BiteBot from Atlanta.
The Problem with Food Logging
I tried to stick with food logging more times than I'd like to admit. MyFitnessPal, mostly. The goal was usually fat loss or body composition — tighten up, pay attention to what I was eating. The pattern was always the same: download the app, commit for a few days, quit within the week.
The problem wasn't willpower. It was that the app was actively subtracting from the willpower it required. Searching the database for "oatmeal" and getting ten nearly-identical entries. Saving a favorite meal, then burning three screens trying to find it again the next morning. Feature after feature bolted on over the years, until the actual act of logging what you ate was buried somewhere under a calendar, a blog feed, and a banner ad.
"Logging your food daily requires a tremendous amount of discipline. Putting ads and friction in front of users actively weakens the drive to manage your diet in a healthy way."
I'd been building AI-native products for a while — daily ops briefings, agent workflows — and the frustration eventually tipped into a question: could I just replace MyFitnessPal with something simpler?
So I built a Telegram bot. Just for me. I'd type "oatmeal with banana and pecans" and get a macro breakdown back. I'd snap a photo of a plate and it would figure out the rest. It worked. Even with pure text commands, logging was significantly faster. The friction was gone.
And then something I hadn't planned for: I kept using it. Even on busy weekends — where the old pattern was always skip one day, then skip the rest. I started leaning on features I hadn't built in on day one: photo analysis for meals I couldn't describe, saved meals for the ones I ate every morning. Once the history built up, I layered coaching on top — and the whole thing became a different experience. The AI flagged trends I hadn't noticed: I was running too high on fat, consistently short on fiber. It helped me land on a calorie target that was realistic for my goals instead of aspirational. For the first time, logging wasn't the goal — the insight was.
"I stuck with logging even on busy weekends. The three-days-and-quit pattern just broke."
That Telegram bot became BiteBot — now in TestFlight beta, heading to the App Store. I'm building it in public, using it every day, and letting real data drive every decision. If it can make food logging effortless for someone who quit every nutrition app they tried, it can work for anyone.
Questions, feedback, or just want to say hi? Email hello@bite-bot.app.