Make the edit mode of the mobile app compatible with OxF

[teolemon]

Problem

• If we ever want to have an app able to handle any kind of product, the edit mode has to behave differently

Make the edit mode compatible with Open Beauty Facts, Open Pet Food Facts and Open Products Facts

Beta Give feedback

1. Add a DEV mode variable for all products which is always "off" by default and that will be piloted server side in the future.
2. Change this DEV mode variable for all products to opf or obf if the DEV mode base url is updated to anything in openproductsfacts.org or openbeautyfacts.org
3. Override texts (change "Ingredients & origins" to "Components" for "opf")
4. Add Period after Opening support for "obf" #5580
   ✏️ Editing 🧴 Open Beauty Facts +2
5. Add a "Properties using Folksonomy Engine" placeholder for "opf" #5581
   folksonomy engine ✏️ Editing 📸 Open Products Facts +3
6. Change the default list of nutrients for "opff" (and/or ensure the server side API is helping) #5582
   🐾 Open Pet Food Facts +1
7. Add support for the Folksonomy Engine in the mobile app (Tracker issue) #697
   2 of 8
   Epic folksonomy engine help wanted 🎨 Mockups available 🎯 P1 📸 Open Products Facts +6
8. Disable "Nutrition" section in full edit mode on Open Beauty Facts ("obf") and Open Products Facts ("opf") #5569
   📸 Open Products Facts 🧴 Open Beauty Facts +2
   
9. Override icons (fork and spoon icon for "categories edit" on opf, obf, opff to an edit pencil) #5576
   ✏️ Editing 🐾 Open Pet Food Facts 📸 Open Products Facts 🧴 Open Beauty Facts +4
   

Part of

• 🐾 📸 🧴 OxF (Compatibility with Open Beauty, Pet Food and Products Facts) tracker #4543

[monsieurtanuki]

If we ever want to have an app able to handle any kind of product, the edit mode has to behave differently

@teolemon For the moment we only have one kind of Product.
Do you expect all kinds of products to fit into that unique class, or should we create classes like BeautyProduct, PetFoodProduct and GenericProduct?

[teolemon]

@monsieurtanuki yes, @stephanegigandet is working on that at the moment.
The data structure will be mostly the same, and we will only remove fields (eg nutrition).
Fields additions are likely to happen in the Folksonomy Engine.
I have clarified the issue to mention that we can honor a product type for all products, based on the root URL in DEV mode, and that as soon as we have a universal scan api, we can honor the product_type from the server