-
-
Notifications
You must be signed in to change notification settings - Fork 280
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
Refactoring of the OCR page UI/UX #5047
Comments
Eventually, we're going to have a "Report image" button, in conjonction with https://github.com/openfoodfacts/nutripatrol/issues |
@teolemon @M123-dev My point here is to have #5027 merged: I've just added a couple of buttons, as required by #5020. |
Hello, Here's a screen I made in 5 minutes, but where I try to address the hierarchy problem.
The actions for the photo shouldn't be on this screen: that's not its role. As I have said, this is just a quick mockup, so feel free to add your suggestions. |
@g123k I believe the point of that screen was the OCR - or at least photo upload. Therefore something more like that:
That said, in your screenshots I see a button that would help us: a single "modify photo" button. Instead of our current 4 buttons ("edit", "select an existing photo", "take another one", "unselect"). The "modify photo" button would go to the existing photo manager (screenshot 2 in the OP). |
The "Edit picture" button was indeed there to redirect to the other screen, because we have 11 actions: And I think that the OCR should be limited to "Extract ingredients": all other actions have no direct link to Ingredients. |
I have no strong opinion on the subject. Except that those are "OCR" pages. |
cf. #3975 too. |
But for the UI: Having the buttons directly above the Image isn't great. Especially for the ones which tend to are very stretched.
Maybe we should align them to the top,
Maybe move the image above them
Make the buttons (which are of lower priority?) a drop down
Any suggestions @g123k @teolemon @AshAman999
Originally posted by @M123-dev in #5027 (comment)
The text was updated successfully, but these errors were encountered: