2 days in, disappointed.
2 days into trying this app and I think I’ll be going elsewhere.
For one, all of the food I logged yesterday transferred over to today’s counter, it didn’t reset. Looking at yesterday’s log, it only saved a couple items, not all of them. It also multiplied one of my item’s values by like 30x, even though it was right the day before. So it screwed up yesterday’s data and didn’t reset the data for today.
Serving sizes are very unintuitive or bugged. For example I created the “food” milk, as you have to manually create each food/ingredient by typing it in or using their AI. Anyways I set the serving size to match the nutritional facts, which was 1 cup. Then when I go to log Milk as being consumed, I entered 1 Cup as the serving and it multiplied the nutritional values by like 480x. If I set the serving to 1ml, then it would give the original nutritional values I set for 1 cup. (Yes, I did go back to make sure everything was up as 1 cup, not 1ml). I could fix this issue by just setting it to “1 serving” as the unit but then you don’t know how much 1 serving is.
I could’ve put up with the serving size issue but the fact that basic logging functions don’t work is a no-go. Shame because the app premise itself is nice for being free, but seems like a vibecode project the way basic functions don’t work.
For one, all of the food I logged yesterday transferred over to today’s counter, it didn’t reset. Looking at yesterday’s log, it only saved a couple items, not all of them. It also multiplied one of my item’s values by like 30x, even though it was right the day before. So it screwed up yesterday’s data and didn’t reset the data for today.
Serving sizes are very unintuitive or bugged. For example I created the “food” milk, as you have to manually create each food/ingredient by typing it in or using their AI. Anyways I set the serving size to match the nutritional facts, which was 1 cup. Then when I go to log Milk as being consumed, I entered 1 Cup as the serving and it multiplied the nutritional values by like 480x. If I set the serving to 1ml, then it would give the original nutritional values I set for 1 cup. (Yes, I did go back to make sure everything was up as 1 cup, not 1ml). I could fix this issue by just setting it to “1 serving” as the unit but then you don’t know how much 1 serving is.
I could’ve put up with the serving size issue but the fact that basic logging functions don’t work is a no-go. Shame because the app premise itself is nice for being free, but seems like a vibecode project the way basic functions don’t work.
Show more
