-
-
Notifications
You must be signed in to change notification settings - Fork 285
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
Product addition (tracker) #1379
Comments
@monsieurtanuki a quick and dirty fix would be one button per pipeline in the addition screen (plus two concatenations of editing sections) |
@teolemon The pipelines (actions behind "help!" buttons) do not exist yet, right? I would even put the "help!" buttons on top, as it's probably what users want first. I mean, 1 star users may want an answer quickly, rather than contribute with pictures that they already see (no added value for them) (plus the gamification: as a user I see that my first inputs already have an impact). |
|
@teolemon Something like that?
|
Looks reasonable. Bugs to open
|
|
@teolemon Something like that? Regarding a short "add THE product category", it means that we'll have to maintain 3 labels:
Same for nutrition facts and ingredients, right? |
yes, much better 👍 |
and the grey nutri-score is replaced by the actual one, as soon as we have it |
After discussing the issue with @teolemon, here is my opinion on implementing a new product addition pipeline. The idea is to assist the user with information predicted by Robotoff during the product addition process. I would suggest to set up the following simple pipeline with the following screens:
We should send data points as soon as the user submit the data at each pipeline stage, to be sure we get partial data in case the user drops the product addition. I don't think it's valuable to talk about ecoscore or nutriscore at the beginning of the pipeline, as the user doesn't necessarily know what these scores are about. I think the user expect to have to provide some data to get information about the product, he/she just needs to be guided. |
@raphael0202 I have no idea what users expect, but it would be fair to assume that at some point nutriscore and ecoscore mean something for them in the app, as:
We could dismiss the nutriscore / ecoscore input in the "add new product" page for users that say they don't care about those attributes. That said, my point here was to code a quick fix (slightly better looking, more interactive) by adding a couple of buttons. |
@monsieurtanuki My point about the ecoscore/nutriscore wasn't very clear, sorry for that. I was taking the perspective of a user in a country with low product coverage (such as Romania, where we're gaining some traction lately), where the user has a high chance of scanning a product not referenced by Open Food Facts. As such, his/her first "interaction" with nutriscore/ecoscore would be in the product addition page, and I find this a bit confusing. I think it's a good time to implement a first version of the pipeline, as it would bring more value than quick fixes (and it's something that we have been postponing for a long time, we already talked about this for the old android app). It's not an issue if images are not uploaded on time, as ML predictions only come as a bonus, it should be possible to complete the pipeline without it. This can be implemented step by step, we don't need to implement the full pipeline now. Just adding step (2) (asking for product name + weight + Robotoff weight prediction) could be a good start. I'm also curious about your feedback on this proposal @teolemon @g123k |
Composite pipelines
We need to wire existing editing components to Robotoff (including for existing products)
Easy
Harder
Better Eco-Score and Nutri-Score onboarding
Be tougher on incomplete products / Towards personal pipelines
|
Who for
What
Product addition
More substantial addition
Done
Video
https://photos.app.goo.gl/V1cwkaVEM9ArwJBL7
Part of
The text was updated successfully, but these errors were encountered: