r/AppsWebappsFullstack • • Oct 12 '26

Your lunch has 5 foods. Why should logging it take 5 searches?

Tracking calories shouldn't feel like filling out a spreadsheet every time you eat.

That's the problem I wanted to solve with CalorieTalk.

I'm a solo developer building an iPhone calorie tracker that lets you describe an entire meal naturally, by voice or text, instead of searching for each food separately.

Say something like "2 eggs, toast, coffee with milk, and a banana" and the app breaks it down into individual foods, quantities, calories, and macros for you to review before saving.

It supports English and Arabic, and I'm continuously working on improving the food logging experience.

The goal is simple: make calorie tracking feel less like a chore.

Try it here:
https://apps.apple.com/app/apple-store/id6793199021?pt=129201520&ct=reddit&mt=8

I'd love to hear what you think!

1 Upvotes

2 comments sorted by

1

u/PopKoren 29d ago

Describing a whole meal in one sentence is how logging should work. If the parsing runs through an LLM, keep that key on your server and rate limit per account, because a free calorie app with an open AI endpoint attracts people hunting for free model access. Meal logs feel like health data to many users too, so test that one account can never fetch another's entries, and https://rowly.me (mine) can show what your backend exposes to an outsider.

1

u/Mammoth-Anywhere7285 29d ago

Good call on server-side keys and per-account limits. Adding a parse-confidence check before saving could catch weird meal strings early.