25
edits
Project:Food Rescue/Features: Difference between revisions
added one feature
(added one feature) |
(added one feature) |
||
| Line 11: | Line 11: | ||
#'''Showing per-product expiry duration.''' This is a low-hanging fruit as the OFF database contains expiry dates but they are not yet shown anywhere in the OFF Android app. The information should be shown as minimum ''duration'', and that information will already help to rescue some food. Example: when crisp bread is meant to last 18 months and it is 2 weeks over the date, it is very probably safe to eat. | #'''Showing per-product expiry duration.''' This is a low-hanging fruit as the OFF database contains expiry dates but they are not yet shown anywhere in the OFF Android app. The information should be shown as minimum ''duration'', and that information will already help to rescue some food. Example: when crisp bread is meant to last 18 months and it is 2 weeks over the date, it is very probably safe to eat. | ||
#'''Showing per-category expiry distributions.''' From per-product expiry dates, diagrams for each category can be created that show shelf life durations of all other products in the same category, and where the currently analyzed product falls in. That should already allow users to know when they can be more relaxed about a specific product, and would allow them to rescue some food items. | #'''Showing per-category expiry distributions.''' From per-product expiry dates, diagrams for each category can be created that show shelf life durations of all other products in the same category, and where the currently analyzed product falls in. That should already allow users to know when they can be more relaxed about a specific product, and would allow them to rescue some food items. | ||
#'''Real storage life label.''' A labelling system, including a good graphical design for the label and its color coding, that informs users at a glance about its real-world storage life duration and how careful one has to be when it expires. This would be placed into the product's summary view in the Open Food Facts Android app, which covers only the lower 20% of the screen after scanning a product. | |||
#'''Edibility information per category.''' Open Food Facts has detailed categories of products already, and it seems that they are applied like tags: each product can be in any number of categories. By attaching the expiry information to these categories, it will be simple to provide all food items with relevant expiry-related information. This information should come in multiple levels of detail, from a one-glance label that indicates if a food item's storage life is "problematic" or not, to summaries, to all the details incl. references to journal articles etc.. The multi-level approach allows to write about the most general methods ("smell and taste") in the most general categories of food items, and that information will then be displayed along more specific information (if available). The app would show the most specific content first, then moving to content from the more and more general categories. This way, a user can stop reading when encountering information that they have seen before. The articles would contain: | #'''Edibility information per category.''' Open Food Facts has detailed categories of products already, and it seems that they are applied like tags: each product can be in any number of categories. By attaching the expiry information to these categories, it will be simple to provide all food items with relevant expiry-related information. This information should come in multiple levels of detail, from a one-glance label that indicates if a food item's storage life is "problematic" or not, to summaries, to all the details incl. references to journal articles etc.. The multi-level approach allows to write about the most general methods ("smell and taste") in the most general categories of food items, and that information will then be displayed along more specific information (if available). The app would show the most specific content first, then moving to content from the more and more general categories. This way, a user can stop reading when encountering information that they have seen before. The articles would contain: | ||
#*Instructions to assess the edibility of expired food items, including a risk assessment in case of mistakes, and an assessment of how simple or difficult the assessment of a certain category of food is. This (risk and simplicity) should be displayed in a fast-to-understand way, using a kind of self-defined categorization scheme. The idea is that the "risk-free and easy" cases should be encouraging for new users to try, to then work their way up to the others over time. | #*Instructions to assess the edibility of expired food items, including a risk assessment in case of mistakes, and an assessment of how simple or difficult the assessment of a certain category of food is. This (risk and simplicity) should be displayed in a fast-to-understand way, using a kind of self-defined categorization scheme. The idea is that the "risk-free and easy" cases should be encouraging for new users to try, to then work their way up to the others over time. | ||