Add the % in the personal match score

[monsieurtanuki]

What

• Related to that, is it planned to add the % score on the mobile app, like we have on the website?

Originally posted by @stephanegigandet in openfoodfacts/openfoodfacts-dart#785 (comment)

Part of

• Personal search (tracker) #1284

[teolemon]

From Google Maps, notice the explanation of the score, and the link to provide feedback:

[monsieurtanuki]

@teolemon For each product attribute that is in the user preferences, we typically have four states: does not match, may not match, unknown match, and a score.
What we would need are:

• collection of "does not match" attributes
• collection of "may not match" attributes
• collection of "unknown match" attributes
• list of attributes, sorted by descending score contribution

With that we would be able to list the top 3 attributes that explain the score/percentage/match, wouldn't we?

[stephanegigandet]

What we do on the website is that we just sort the attributes we display below the score by importance: the mandatory ones first, then very important, then important. Always in the same order.

It works well to explain the score in almost all cases (the case where it doesn't work is if you say you are allergic to 10 different allergens, then it would be useful to display the non-matching first).

For this kind of feature, I would really recommend that we do the same thing on both the app and the website. We should try to have a seamless experience.

If we decide that there's a better way to present the information, we can then work to implement it on both the app and website.

[monsieurtanuki]

What we do on the website is that we just sort the attributes we display below the score by importance: the mandatory ones first, then very important, then important. Always in the same order.

Same behavior in the app.

It works well to explain the score in almost all cases (the case where it doesn't work is if you say you are allergic to 10 different allergens, then it would be useful to display the non-matching first).

Fair enough.

For this kind of feature, I would really recommend that we do the same thing on both the app and the website. We should try to have a seamless experience.

The size of the screens do have an impact, though.

If we decide that there's a better way to present the information, we can then work to implement it on both the app and website.

Maybe we have more flexibility in the app with the dev mode.