-
Notifications
You must be signed in to change notification settings - Fork 14
Bad UX. "Risiko Begegungen" are not reflected in the "Risiko Status" #113
Comments
Related: #100 |
Maybe change "Risiko Begegnungen" to something like "Begegnungen mit Infizierten", that is: remove "Risiko" from that text. |
Now its called "Risiko-Begegnung mit niedrigem Risiko"
|
The associated confusion hit mainstream media: https://www.tagesschau.de/inland/corona-warn-app-risikoermittlung-101.html Edit: Given a project budget of 68 000 000 € and a bug report rotting for more than month as of today, it is somewhat peculiar that tagesschau is in the need to explain the UX. |
@daimpi - I don't see any relevant change: The initial problem remains. The App lists risky things "1 Begegnung mit geringem Risiko" but the risk status "green" does not change. As I said before: If there is a risk by these encouters, this has to be reflected in the total risk status. But in the new screens, the risk relfected in the text componenent is not reflected in the card component (green). The generated confusion is discussed at various web pages.
Trying to do some "Think aloud" (https://en.wikipedia.org/wiki/Think_aloud_protocol), I come up with this these questions:
Some ideas:
IMHO people tent to understand the "Risiko" as the actual result, cause the App as a whole is used to estimate the Risiko. IMHO this is the actual confusion expressed by all media sources discussing "Begegnungen mit Geringem Risiko". For this, it's a bad thing to even label presumably harmless encounters as some kind of "Risiko". |
Just a small remark from me: |
Yes. Which is even more confusing, cause "niedriges Risiko" in the encounter is not "niedriges Risiko" in the card. People expect some relation - same name -, but it is still uncomprehensible. |
Also there is a huge long explanation text if you tap on the card.
Yes, if the "Risikobegenung" is longer than 14 days ago. |
Edit - sorry, missed that point
this somehow misses the point of the think aloud protocol. These questions should be answered in the App, not on github... The question is raised, because the relationship of "für ihre Risikoermittlung wird nur der Zeitraum der letzten 14 Tage betrachtet" and "Dennoch als niedrig eingestuft" is confusing. IMHO it is not comprehensible, to what extent the counter is impacting the estimated risk ... and if the note on 14 days also applies to the counter. E.g. having "in der Corona-App wird nur der Zeitraum der letzten 14 Tage betrachtet" is better, imho. |
P.S. I'd like to make this explicit https://www.corodok.de/app-risiko-ohne-risiko/ boils it down to: "Es gibt also eine Warnung, bei der man nichts tun muß, ein Risiko ohne Risiko." IMHO this is also a good way of describing the associated confusion P.P.S.
IMHO, this would remove some confusion. |
Heiho,
I proposed to relabel it. It's fine to have such a counter. But this value is way too "raw" to express some kind of risk. It's a parameter for calculating the risk. It does not express any risk by itself. ... just give it a proper label. Take it this way: The point is, that the UX mistakenly suggest that this value determines some total risk to a certain, comprehensible and relativly higher degree. This is not given. |
Please show Date and Time of later on announced risk contacts, even if this leads to still having a green status. As such contacts might occur only at shopping or eating in a restaurant, one can reconstruct with Date and Time where one habe been and if shopping or queuing anywhere is the risk reason. This would enhance the analyse and discussion and avoiding of behavior in the future much, when it ia shown if the risk contact was at 8:00 in the bus ir at 12:00 in the McDonalds restaurant or at work at 10:00 o'clock at a certain date/day. so it is not about "10 days ago" but about exact time and day. Thanks for implementing that local showup fast. |
Unfortunatly, this is OT as of this issue. Please check other, already existing tickets or have a look at https://github.com/mh-/corona-warn-companion-android |
Mainstream media still is still discussing the issue, while the bug is still rotting in the tracker: |
With ENFv2 used in the newest app version, some of the suggestions were addressed: Harmless encounters with distance > 8m (73dB signal strength) and duration of less than 10 minutes are filtered out by the app and are not displayed as risk encounters. See https://www.coronawarn.app/en/faq/#encounter_count_19 for details. Corona-Warn-App Open Source Team |
Sure about the ticket? That's not suggested in this one. |
@yanosz Yes, in particular, harmless encounters are now filtered and multiple low risk encounters count towards a total risk score that can lead to an overall high risk. Corona-Warn-App Open Source Team |
@heinezen : To avoid misunderstandings: Filtering harmless encounters is not part of this ticket. This ticket addresses the UX mismatch between risk expressed in different components: Are status and counter aligned as of now? I.e., does an increasing counter result in risk status red as of now? |
@yanosz You mentioned harmless encounters in your introduction, so I thought this information would be useful here. Sorry if it was confusing.
Yes! This is what I wanted to say. The ENFv2 evaluation considers multiple this now. The normalized exposure time of low risk encounters is summed up for the day. So multiple low risk encounters will lead to a high risk score if the sum of their individual score is higher than the "high risk" threshold. See here for more information: https://github.com/corona-warn-app/cwa-documentation/blob/master/images/risk_calculation/risk_calculation_enf_v2_overview.pdf |
I think the confusing fact is, that the number shown is not the sum of the risk scores. |
closed, fixed |
Current Implementation
Presumably harmless encounters (e.g. short distance, short time), are displayed as risky "Risiko-Begungen". Nevertheless, they do do not have a noticeable impact on the risk status (e.g. green).
This is confusing. It is warning people about risky things, but the risk doesn't change.
Suggested Enhancement
Reconsider the UX, for instance:
Mögliche Risiko Begegnungen" "Infizierten Begegnungen"Show seperate counters "Risiko Begegnungen" and "Nicht Risiko Begegungen"Rule of thumb: If there's a risk solely triggered by presumably harmless encounters, than it has to be reflected in the total risk status, e.g. Relabel the risk status to "Leicht Erhöht", when encountering such contacts.
Expected Benefits
UI-Consistency:
Internal Tracking Id: EXPOSUREAPP-2061
The text was updated successfully, but these errors were encountered: