I want a refund
The AI voice recognition is even worse. I said very simply “two scrambled eggs with 25g of cottage cheese fried in a little bit of olive oil” and it interpreted that as one egg, fish and chips, cheesecake, and fried calamari.
I want a refund.
Response from developer
Thank you for the detail — that is a bad first experience and the specifics help. Both problems you hit come from the on-device recognition in this version. We have rebuilt photo scanning entirely: it now runs on a much larger cloud model instead of the on-device one, and results arrive as an editable estimate you can correct before saving. Voice logging has also been reworked. If you would like a refund, Apple handles those at reportaproblem.apple.com. If you would rather wait and try the new version, we would genuinely like to know whether it holds up for your meals — calometric.app/support reaches us directly.
Ok Tracker Without Subscription
Not as good as I once thought. The app is good at barcodes and reading nutrition labels but unfortunately has a hard time customizing food if you cook your own food. When adding 100g chicken breast, it was 0 calories with 0 grams of protein. Also no way to edit calories, fat, protein on custom meals.
Original Review:
So far this is the best calorie/food tracker without a subscription. Nice, clean, and organized. Even has a widget when you’re looking at your calorie intake a glance.
Response from developer
Thank you for updating your review — a custom food saving as 0 calories and 0 g protein is a bug, and being unable to edit macros on a custom meal is a gap we should have closed. Both are on us to fix, and the meal review step has been reworked so that every value — foods, portions, servings, calories, carbs, protein and fat — is editable before you save. If a custom food still comes out empty for you after the next update, please send us the exact entry at calometric.app/support. Glad the barcode and label scanning are working for you in the meantime.
Every picture is treat as an error
Response from developer
Thank you for reporting this — every photo being rejected is a real bug, not intended behaviour. The photo path has been rebuilt since this version and no longer uses the on-device classifier that produced those rejections. If it still happens for you after the next update, please send us an example at calometric.app/support and we will chase it down.
Good app, but can't set exact units
That makes tracking a little inaccurate.
Response from developer
Thank you — this is a clear bug. Decimal amounts should be enterable, and on a comma-decimal keyboard they should accept a comma. We are treating this as an input-handling fault rather than a design choice, and it is on the list. If you can tell us which screen you hit it on — meal review, custom food, or goals — that would help us reproduce it exactly: calometric.app/support.
