[UI/UX] Simplification of the user interface for non-technical people

[linux-lukas]

A. Problem / Aim

The report generated by the "webbkoll" project is detailed and certainly easy to read for technically (very) experienced people. For non-technical or less technical people, the report can be very overwhelming because it is very technical without explaining in simple language which problems (of a legal nature, for example) the website has that the $user wanted to check with webbkoll.

The aim would be to simplify the UI/UX of the "webbkoll" project to the extent that it explains in simple language what is problematic and why, and how this could be prevented (in the future).

B. Solution

With regard to UI/UX in general:

Individual sections in colour-coded boxes with rounded corners.

With regard to wording:

What easy-to-understand descriptions for non-technical or less technical people might look like, I think, can be found well in the glossary of the Exodus Privacy project: https://reports.exodus-privacy.eu.org/en/info/understand/

In addition, very long explanations should be avoided, because this is simply overwhelming.

With regard to function enhancement:

Export the report in easy language as a .pdf file to be able to show it to the supervisor and a table which evaluates the website according to objective criteria based on the established result.

C. Alternatives

The alternative, if UI/UX simplification were not addressed, would be for users to either first call in friends and acquaintances who know IT, or do without it altogether.

[andersju]

Thanks for the feedback! You're right that the report is currently targeted at tech people. Making it easier to understand for others is a challenge, and it's also a pedagogical problem explaining the limitations - i.e., all the things Webbkoll can't check, for various reasons; you can have a "good-looking Webbkoll report" and still be terrible at privacy.

That said, your suggestions are good and welcome. I don't have much time now, but at some point I hope to start working on a completely new version of Webbkoll, and then I'll keep your suggestions in mind.

[linux-lukas]

Thanks for the feedback! You're right that the report is currently targeted at tech people. Making it easier to understand for others is a challenge, and it's also a pedagogical problem explaining the limitations - i.e., all the things Webbkoll can't check, for various reasons; you can have a "good-looking Webbkoll report" and still be terrible at privacy.

That said, your suggestions are good and welcome. I don't have much time now, but at some point I hope to start working on a completely new version of Webbkoll, and then I'll keep your suggestions in mind.

Thank you very much for your feedback!

For this situation, I had seen a post by a user on Mastodon that might be appropriate:

It contained a picture of labels that can be given to an issue.

The title was "Shelved for lack of staff manpower" and the description "It it not that I do not want it done, it is just that I do not have time to do it".

How do you see it? Would this be an issue label that would make sense to create and assign for this issue?

[andersju]

For this situation, I had seen a post by a user on Mastodon that might be appropriate:

It contained a picture of labels that can be given to an issue.

The title was "Shelved for lack of staff manpower" and the description "It it not that I do not want it done, it is just that I do not have time to do it".

How do you see it? Would this be an issue label that would make sense to create and assign for this issue?

Sounds good, I'll assign something similar!