simonoppowa
Feature Request: Express logged foods in terms of serving sizes
When I scan the barcode on a package of food (e.g. a bag of chips, a can of soup, etc.), it's counterintuitive that the default assumption is that I've eaten 100 grams of the product (rather than 1 serving, as described on the label).
Additionally, if I know I've had some multiple (like 1.5x or 2x) of servings, I'm seemingly expected as a user to open up a calculator app, read the weight off the package, divide that by the labeled "servings per container", and multiply that by the number of servings I've had to get the desired consumption amount in grams (and then switch back to the app, and enter that value).
In competing apps, the looked-up metadata includes the indicated serving size and I can easily just change the default (in servings) from "1" to some other amount (and the other values on the diary entry will scale accordingly). And, importantly, this multiplication is only associated with the diary entry and not the food definition itself (so I can easily have 2 servings today and 3 tomorrow).
Thanks for building this and releasing under the GPL! It's off to a promising start, and with some adjustments I could see it being a daily driver for myself and others.
I totally agree with @BHSPitMonkey. An easy implementation could be to add servings as a possible unit for the items that have a serving size, instead of just g/ml. I would be happy to contribute with this feature, I'm using the app since a couple of weeks and I totally love it, but this feature would be very useful.
This is much needed and as mentioned by @BHSPitMonkey also what is often expected when using a calorie tracker.
For me personally I mostly register by weight but some things, e.g. frozen items like burgers it is much easier to register by servings.
Either way, the current state in the app is a bit counter-intuitive as there actually is a serving size to be entered when creating a new meal item in the app, but then when adding said item to the diary the drop-down containing the unit (g, ml) is disabled (Edit: tagging issue #63). From a UX perspective it seems reasonable to simply have this drop-down be enabled at all times.
