-
-
Notifications
You must be signed in to change notification settings - Fork 400
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add better support for specific diets #9092
Comments
The current setup (see image) works for common allergens but feels rigid and limiting. Plus what do the different settings even mean? What is the difference between important and mandatory? Or very important and just important? A better approach may be a dynamic filtering system where users can input exactly what they want to avoid, are sensitive to, or allergic to—whether it’s specific compounds like casein, additives, or triggers like histamines. This system could include predefined filters for common allergens (gluten, dairy, nuts, etc.) and diets (vegan, keto, etc.) for simplicity, while also allowing users to create personalized filters. For example, a user could exclude components like gluten, alpha-amylase, certain emulsifiers, or maltos. Such an approach would:
Especially with sensitivity testing (eg. IgG4 [independent if they are actually useful for diagnosing food sensitivities]) becoming more and more common, I think this would be a valuable change to OpenFoodFacts. The dietary needs and the motivation to use Open Food Facts are individual. Let's tailor the experience to reflect that individuality. Thoughts? @teolemon Here is an excerpt of what components would be interesting to have as filters. Getreide glutenhaltig (Gluten-Containing Grains)
Getreide glutenfrei (Gluten-Free Grains)
Milchprodukte (Dairy Products)
Gemüse, Salate (Vegetables, Salads)
Hülsenfrüchte (Legumes)
Fleisch, Fisch, Ei (Meat, Fish, Egg)
Obst (Fruits)
Nüsse, Samen (Nuts, Seeds)
Kräuter, Gewürze (Herbs, Spices)
Hefen (Yeasts)
|
Existing
What
Why
Tasks
Assets
See also
Part of
The text was updated successfully, but these errors were encountered: