Answers to the things people ask most. If yours is not here, email sivavimelrajhen@gmail.com.
Log → “Type what you ate”, then write it as you would say it: “2 eggs, toast with butter, large coffee”. Every row shows which fragment of your sentence it came from, and one tap changes any of them.
Tap the row. You get the shortlist it was choosing between, and a search box if none of them is right. Nothing is logged until you press Add.
“200 g”, “200g”, “½ cup”, “1/2 cup”, “2 slices”, “a large”, “2 × 30 g”, “one and a half tablespoons”, “half a banana”, “2 medium bananas”. Plurals work. Say “yesterday”, “this morning”, “last night” or “for lunch” and the entry goes to the right day and the right meal.
That row is telling you it would rather ask than guess. Tap it to pick from the shortlist or search. Anything still unmatched is simply left out when you press Add — it is never logged as a guess.
Because boiled, baked and mashed are genuinely different numbers and it will not pick for you when the gap is close. Where one answer is clearly right — “chicken breast” means the cooked one — it just logs it.
The preview always shows what will actually be logged before you press Add, and a single entry is capped at 5 kg or 10,000 kcal, so a slipped decimal point cannot quietly wreck the day or the target behind it.
Link it. The app asks you which food the packet is, or lets you type the label, and remembers that barcode for good.
Log → Easy mode. Pick how rich the meal was and roughly how big. It goes in as an estimate and is labelled as one. A rough day logged is worth far more than a perfect day missing.
Log → Eating out. Count the plate in palms, cupped hands, fists and thumbs. You get a range; the middle of it goes in the diary.
Because the app measured your energy use again and it had moved. It is not a formula — it is worked out weekly from what you logged and what your weight trend did.
That is fine and it is not held against you. Days with nothing in them are treated as missing information, never as days you ate nothing, and a patchy week simply counts for less.
About two weeks. Before that it uses the usual formula and says so. The first fortnight of weight change is mostly water, so it deliberately counts for less.
The target will not go below what your body uses at rest, and the deficit is capped at a quarter of your measured expenditure. Below that you buy muscle loss rather than faster fat loss.
Because a reading is mostly not body weight. The line is a smoothed trend and the dots behind it are your actual readings. The band around the line is how far your readings scatter — a move inside it is not news.
Sodium, carbohydrate, glycogen water and what is still in your gut. A real gain of one kilogram of fat needs about 7,700 kcal above what you used. More → Why things happen → overnight.
Daily is the most useful if it does not bother you. Two or three times a week is plenty and the trend handles gaps. If weighing is something you would rather not do, the food side works without it.
More → Your data. Plain CSV for the diary, the weigh-ins and the daily totals, or one JSON file that restores the app exactly. No limits and no upsell.
No. What you log lives in the app's own folder, which iOS keeps across updates — the diary, weigh-ins, saved meals, your foods and your settings all come back exactly as they were. Only deleting the app, or the erase button inside it, clears anything.
Save a backup on the old one, move the file across however you like, and restore it on the new one. There is no account and no sync, so the backup file is the only copy that exists outside the phone.
A file would not open, so the app set it aside rather than writing over it — nothing was deleted. Restore your most recent backup from More → Your data. If you do not have one, email us before doing anything else; the original file is still on the phone.
The phone would not accept a write, usually because storage is full. Your change is still on screen but only in memory. Free some space and the message clears itself on the next successful save.
Everything exports as plain, properly quoted CSV, and food names are written so that a name beginning with “=” is treated as text rather than run as a formula. Numbers use a full stop as the decimal separator.
Settings → Privacy → Lock the app. Uses Face ID, Touch ID or your device passcode.
About 770 MB of it is the AI model, which ships inside the app instead of living on a server. That is what lets the whole thing work in aeroplane mode on the very first launch, with no account and nothing to sign up for. You pay it once.
Never. Logging, the food database, barcodes, the trend, the target and the coach all run on the phone. The only thing that uses the network is the optional outside AI service, which is off unless you turn it on with your own key.
It cannot produce one at all. Every figure comes from the food database or from arithmetic on what you logged, and anything the coach writes is checked against those figures first. If the check fails you get the computed answer instead, and the message says so.
Settings → Display for light, dark or system. Text follows the iOS Dynamic Type setting all the way to the accessibility sizes.
EasyFast is a diary, not a clinician. If tracking is making your relationship with food worse rather than better, the right move is to stop tracking and talk to someone — a GP, a registered dietitian, or a national eating-disorder charity. Everything you logged is on your phone and you can export or erase it in two taps.