Skip to content
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

NutriScore v2 positive/negative points are barely readable #6083

Open
g123k opened this issue Dec 29, 2024 · 6 comments
Open

NutriScore v2 positive/negative points are barely readable #6083

g123k opened this issue Dec 29, 2024 · 6 comments

Comments

@g123k
Copy link
Collaborator

g123k commented Dec 29, 2024

Hi everyone!

On the website, it's OK to have points represented by squares:
Image

However, on mobile (an even with a larger width), it's barely readable:
Image

Shouldn't we use a circle like this one?
Image

@g123k g123k changed the title NutriScore positive/negative points are barely readable NutriScore v2 positive/negative points are barely readable Dec 29, 2024
@teolemon
Copy link
Member

We should stay in points, which is the metric of the Nutri-Score.
That could work , but I'd rather have the server adopt it as well

@monsieurtanuki
Copy link
Contributor

Rows of 5 instead of 10 may do the trick.

@g123k
Copy link
Collaborator Author

g123k commented Jan 4, 2025

Rows of 5 instead of 10 may do the trick.

Unfortunately we can't, because it's an SVG (eg: https://static.openfoodfacts.org/images/attributes/dist/points-negative-7-10.svg)
The only way is to create a custom Widget (but I'm still not convinced by the squares)

@stephanegigandet
Copy link
Contributor

Why don't we display the image with a fixed height but variable width, just as we do on the web?
The jauges are compact, but you lose the fact that some nutrients like salt count more than others like saturated fat.

@alexgarel
Copy link
Member

Why not use rectangles instead of squares and fit on one line ?

@g123k
Copy link
Collaborator Author

g123k commented Jan 6, 2025

The issue with rectangles is that we never have the same scale: 10, 15, 20… points.
So for each line, we have to compute: Is a good or bad score?

With percent-like progress, it's way easier to understand if this is good or bad

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Status: 💬 To discuss and validate
Development

No branches or pull requests

5 participants