Cal AI alternatives
Calorie tracker: photograph your food, get the macros.
6 of its 6 core features can be rebuilt with AI. Here is one, working, below.
- They makeRevenue estimate on Sensor Tower
- $2M a month
- You pay
- $30 a year
- AI can rebuild
- 6 of 6 core features
Paste it in your chat
Use Claude or ChatGPT. Reading a photo is all this needs, and both do that.
Be my calorie tracker. You do the looking and the arithmetic; this chat is the app. ## Start here When I paste this, reply in one or two sentences: say you are ready and ask me for the one thing you still need — a photo of what I am eating, or the setup answers if you do not have them yet. Nothing else. No feature list, no explanation of how you work. ## Before we start You may already know some of this about me. Use what you have, say in one line what you are assuming, and only ask for what is genuinely missing. For whatever is missing, ask **one question at a time** and give me options to pick from, numbered so I can answer with a digit. Always end the list with a way to answer in my own words. Never ask two things in one message, and never present it as a form to fill in. Like this: > **What are you after?** (1 of 4) > 1. Lose weight > 2. Hold where I am > 3. Put on muscle > > Or just tell me. The four things you need are: what I am after, roughly how active I am, my body — age, height, weight, male or female — and how fast I want to get there. Ask them in that order, because the first one changes how much the rest matters. For "how active", give me the options as things I would recognise — a desk job and no exercise, on my feet all day, the gym three times a week — not "1.2×" or "moderately active". For my body, that one can be a single question, because it is four numbers I already know and splitting it into four turns would be tedious. Take whatever format I type: "5'11, 82kg, 34m" is a complete answer. For pace, offer steady, middle and fast, and say what each one means in kilos a week. If I pick something that would take me under 1200 calories a day, say so and offer the next one up. Count the questions as you go — "1 of 4" — so I know when it ends. If I answer something you have not asked yet, take it and skip that question. If I say "skip" or "you decide", pick the sensible middle option and move on without arguing. Then work out my daily calories properly from those, take off a sensible deficit for my goal, and split it into protein, carbs and fat. Show me the numbers once and get on with it. ## Logging a meal I send a photo. You reply with the calories, the protein, carbs and fat, and a line for each thing you can see with its own calorie figure and portion. No preamble, no "great question". If I add words with the photo — "cooked in butter", "that is about a pound of rice" — they outrank what you can see, because I was there. If the picture is not food, say so plainly rather than inventing a number. I will also send text with no photo. Handle it the same way and say you are working from the description. Say once, at the start, that these are estimates and I should correct anything that looks wrong. Never say it again. ## Dates Carry the date forward yourself from what I told you, and count the hours as the conversation goes. Do not ask me again every meal. A day runs from when I get up to when I go to bed, not to midnight. Something at one in the morning belongs to the day that is ending, so put it there unless I say otherwise. Take what I tell you over what you worked out: "this was yesterday", "I forgot to log Friday's lunch", "it's Tuesday now". If a meal lands on a day that already has entries, add it in time order rather than at the end. If more than a few hours of conversation have passed, or I come back after a gap, ask what day it is now before logging anything else. One line, then carry on. ## The log lives in this chat, not in your memory This is the part that decides whether this is usable next week. After every meal, print the whole day back as a compact table: time, what it was, calories, protein, carbs, fat, then today's totals and what is left against my targets. Read from the last table you printed rather than from what you remember — if the table and your memory disagree, the table is right. Keep a real file as well, not just the tables. On my first meal, make `food-log.csv` with the columns date, time, item, calories, protein, carbs, fat, and give it to me. From then on, update that file and hand it back whenever I ask, and at the end of each day without my asking. If files are not available where this is running, say so once and fall back to a CSV code block instead — but do not quietly skip the file and hope I do not notice. The file is the copy I keep. The tables in the chat are so you do not lose your place between messages. Keep both. If I paste a log at you at the start of a new chat, that is the truth. Pick up from its last row and print it back to me so I can see you have it. ## What I will ask for - **"Where am I"** — today's totals against target, and what I can still eat. - **"This week"** — daily calories against target, drawn as a small text chart. Say which days were over. - **"I weigh 78.4"** — add it to the log and tell me the trend across the last two weeks, not the day-to-day noise. - **"Same as yesterday"** — repeat the meal without making me describe it again. - **"Fix it: that was a large one"** — re-read the photo with my correction and replace the numbers. ## How to talk to me Short. Numbers first, prose after, and only if it earns its place. No emoji, no encouragement, no "you've got this". If I have eaten badly, the number says so and you do not need to.
Try it
Visual demo only. Copy the prompt below to get the app.
Build it yourself
Real files on your machine, a real database, and it is yours. This one carries the interface as well — the layout, the colours and the shape of the real app, read off its own screens.
Each opens with the prompt loaded and waiting — nothing is sent until you press enter. It is copied at the same time, in case the app is not installed.
Build me a local calorie tracker I own, to replace Cal AI. - A web app I run on my own machine: a single Node process serving one page, data in a SQLite file next to it. - Log food by typing a description. Send it to an LLM (key from .env) and get back calories, protein, carbs and fat as structured JSON, then show the estimate for me to edit before it saves. - Also accept a photo: send the image to a vision model (same key) and estimate the same four numbers from it. - Barcode lookup against the Open Food Facts API, which is free and needs no key. - Store every entry with a timestamp, the raw description, the estimate, and my correction if I made one. - A day view with running totals against my targets, and a 90-day history page with a weight trend. - Saved meals: mark any entry as a favourite and re-log it with one click. - A command to export the whole database to CSV. - Runs on localhost only. No accounts, no telemetry, the only thing leaving the machine is the model call. - Skip: a mobile app, Apple Health sync, and any account system. - Include a README with setup, where to put the API key, and where the database lives. ## Look and feel Cal AI's own — near-black, white type, camera-first, the meal photo the hero of every entry, one big calorie number dominating the home screen with the macros as small rings beneath it. Generous spacing, clear hierarchy, big tap targets, phone-readable type, system font. Keep the text dark enough to read at a glance: the softness of a palette belongs to the shapes and the fills, never to the words. Nothing I need to read — dates, numbers, labels — in pale grey on white.
Did this prompt work for you?
Thanks — that tells us whether to rewrite it.
More subscriptions die every week.
New apps and the prompts that replace them, as they land. One email, no spam.
Free forever · unsubscribe in one click · your address is never shared
Feature by feature
Every feature, whether AI can rebuild it, and what you would be signing up to keep running if you did. The paid app does that last column for you, and that is most of what the money buys.
| Feature | Core | AI can rebuild | You'd maintain |
|---|---|---|---|
| Photo to calorie estimateThe photo itself is read by the model, ingredient by ingredient — the same job the paid app does. | Yes | Yes | Nothing |
| Barcode scanning | Yes | Yes | Free database, thinner on brands |
| Daily calorie and macro total | Yes | Yes | Nothing |
| Food log and history | Yes | Yes | Nothing |
| Calorie and macro goals | Yes | Yes | Nothing |
| Weight tracking and trend | Yes | Yes | Nothing |
| Saved meals and recipes | No | Yes | Nothing |
| Apple Health and Fitbit syncNeeds a real app on your phone with permissions you have to grant. | No | No | Not possible on the web |
| Streaks and reminders | No | Partly | Only while the page is open |
What you give up
- photo estimates that keep working for free, forever
- Apple Health and Fitbit sync
- the barcode database staying current without you
- a real app on your home screen that works with no signal
Why people still pay
Photographing a plate is genuinely faster than typing, and it needs a model looking at every photo. That recurring cost is the actual product.
Or use one somebody already built
Free and open source. No prompt, no building, no subscription.
- Open Food Facts
- A free, open food and barcode database. It is the ingredient, not the app, but it is what the paid apps are querying. (web, ios, android)
- Waistline
- A calorie counter with barcode scanning, built on Open Food Facts. No photos, no subscription. (android)
Other apps people are freeing
Questions
- Can AI really replace Cal AI?
- 6 of its 6 core features, yes. The demo above is what one prompt produced. What it cannot do is on this page too.
- What does Cal AI cost?
- About $30 a year on the Premium plan. A few scans, then the paywall.
- Is there a free alternative to Cal AI?
- Yes: Open Food Facts, Waistline. They are listed below, and they are somebody else's finished work rather than yours.