Difference between revisions of "Mobile App/Classic App Features"
Jump to navigation
Jump to search
m (Teolemon moved page Mobile App/Features to Mobile App/Classic App Features without leaving a redirect) |
|||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
[[File:Google Play logo.png|thumb]] | [[File:Google Play logo.png|thumb]] | ||
− | + | [[Category:Features]] | |
=== Current features === | === Current features === | ||
* Product scan | * Product scan |
Latest revision as of 16:19, 14 August 2024
Current features
- Product scan
- Ingredient analysis
- Scan history
- Editing
- Personnalisation of product page
- Offline cache
- Offline edit
- Dark mode
- Product lists
- Personalized comparisons
- Flexible product page using server-driven Knowledge Panels
- Login, Signup
- …
Feature proposals
- People expect nonobtrusive experiences from Open Food Facts (access to information not blocked by login, but also, very easy path to sign-up, login and X device sync, which we don’t offer).
- We also want the app to feel very reliable, and it should never feel unresponsive, slow, of disconnected.
- People expect value added deciphering, in context, and they need to feel the advice is personalized for them.
- This advice should be available in any condition, especially if the product has been scanned. A modicum of all the database should be available offline, and everything that has been seen before should be stored for instant viewing, with mechanisms to purge.
- The app should make provisions to accommodate non-food products in the future (cosmetics, others). Enabling cosmetic scan in Open Food Facts
Scan
- Scan should be continuous, and instant (with a local copy of the essential information available offline), in all directions, and work in bad conditions (low light, bad camera, 90 angle, broken main camera)
- The result should display what it currently does on Android: Nutri-Score, NOVA group, CO2, # of additives (along with a first time explanation to scroll up the scan card for more details and explanations), diets if not disabled, and allergen warnings if enabled
- Scan requests should be specified as such to the server, with an HTTP header. They should use the fields= API to minimize payload.
- Spec not yet developed in Scanning barcodes
Product addition
Balanced diet support
Towards support for balanced diets
Robotoff questions
How to implement the blue questions
Ingredient analysis (vegan, vegetarian, palm oil, and more in the future)
Ingredient analysis specification
Additives cards
Mobile gamification and playfulness
Mobile gamification and playfulness
Allergies
We need to be very clear upfront that data might be incorrect, and that detection might be incorrect. We thus offer allergen detection as a time-saving feature, but the final check should be manual from the packaging.