Firstly, trace ingredients are often what's important to the consumer. Fine, I know my peanut butter is mostly peanuts, but how much salt is there?
Secondly, these are simple examples. What do you do with, say, a can of chicken and vegetable and noodle soup, which could easily have thirty ingredients before you even start counting the potentially-nasty additives down in a tiny box in the corner.
Thirdly, apparently labellers aren't obliged to split up certain categories (eg broccoli, sugar snap peas, green beans and carrots are all in a single green square). So presumably this doesn't even solve the specified problem of not knowing how much white vs whole wheat is in your food -- why would you split up white and whole wheat into separate categories when beans and carrots are the same?
I didn't think the #1 entry was very practical either, but the full list of entries is worth a look. There are some good ideas and more realistically usable designs in there. GOOD just isnt likely imo to choose winners based on usefulness over beauty.
> Secondly, these are simple examples. What do you do with, say, a can of chicken and vegetable and noodle soup, which could easily have thirty ingredients before you even start counting the potentially-nasty additives down in a tiny box in the corner.
How about inverting the tree-map such that the smaller the amount, the greater the portion of the tree-map taken up? You're going to need all of that space anyway for the names of those potentially-nasty additives to be printed in a legible font size...
A few friends of mine built something similar. Loaded the USDA nutrition database in a dropdown, and scaled 24 vitamins, nutrients, calories, etc by recommended daily intake:
Many people have told me an added layer of discovering foods with particular nutritional qualities (filtering, sorting) would be very appealing. A recommendation engine for food.
If you're looking to hack on the dataset, check out this JSON version:
can they make a side by side comparator? it doesn't have to actually compare, can be just another frame ( or frames) where I can select the same and do the comparison myself.
For example I want to see the differences in raw broccoli and steamed broccoli.
IMHO, the Nutrition Information box is actually a shining example of good design already. It is very, very legible and has a clear information hierarchy.
The problem with this exaple is that it's hard to see quickly what the key points are, since prominence is automatically given to higher scores, whether they're good or bad.
This is pretty bad I think. The amount of substance by mass is nearly completely unimportant. Consider a package which has 99.999% Organic Apples and 0.001% Plutonium. But hey, it's 99.999% organic! Look at all that red!
Much better is a simple ordered list of ingredients, so we're not bamboozled into ignoring certain ingredients just because they're not the majority of the content. But wait, thats ... what we already have on our packaging? What good visualization!
15 comments
[ 2.9 ms ] story [ 44.8 ms ] threadFirstly, trace ingredients are often what's important to the consumer. Fine, I know my peanut butter is mostly peanuts, but how much salt is there?
Secondly, these are simple examples. What do you do with, say, a can of chicken and vegetable and noodle soup, which could easily have thirty ingredients before you even start counting the potentially-nasty additives down in a tiny box in the corner.
Thirdly, apparently labellers aren't obliged to split up certain categories (eg broccoli, sugar snap peas, green beans and carrots are all in a single green square). So presumably this doesn't even solve the specified problem of not knowing how much white vs whole wheat is in your food -- why would you split up white and whole wheat into separate categories when beans and carrots are the same?
How about inverting the tree-map such that the smaller the amount, the greater the portion of the tree-map taken up? You're going to need all of that space anyway for the names of those potentially-nasty additives to be printed in a legible font size...
You could put it on a log scale. Probably still confusing to people not familiar with logarithms.
http://exposedata.com/intake/foodpick.html (takes a minute to load)
Many people have told me an added layer of discovering foods with particular nutritional qualities (filtering, sorting) would be very appealing. A recommendation engine for food.
If you're looking to hack on the dataset, check out this JSON version:
http://ashleyw.co.uk/project/food-nutrient-database
can they make a side by side comparator? it doesn't have to actually compare, can be just another frame ( or frames) where I can select the same and do the comparison myself.
For example I want to see the differences in raw broccoli and steamed broccoli.
Here are a few other concepts we messed around with:
http://fleetinbeing.net/intake/web/rdi.html (stacked bars)
http://fleetinbeing.net/intake/web/groups.html (hover to see vegetable/nutrients)
http://fleetinbeing.net/intake/web/matrix.html (matrix plot)
The problem with this exaple is that it's hard to see quickly what the key points are, since prominence is automatically given to higher scores, whether they're good or bad.
Much better is a simple ordered list of ingredients, so we're not bamboozled into ignoring certain ingredients just because they're not the majority of the content. But wait, thats ... what we already have on our packaging? What good visualization!