Initially Written written by Diarmid Mackenzie, Weds 15 April. Minor feedback from Steve Penrods applied. More feedback welcome (add comments, or edit directly - new content, or clarifications: just go ahead. If you want to delete or substantially rewrite existing stuff please comment & discuss first).
At the time, I was very focussed on Safe Paths app. Does this need more extension to reflect all stakeholders/value from Safe Places? (almost certainly, yes).
...
Attribute | Illustrative statement (not comprehensive) |
Precision of Info | When I overlapped with someone I want to get specific information (arrow narrow time window, specific place) |
Accuracy (False Positives) | I don’t want to be warned about encounters where there was no plausible risk of infection |
Accuracy (False Negatives) | If I have an encounter with someone that risks infection, I want to be notified |
Reliability (foreground) | I want the app to work when I try to use it. No hangs, crashes etc. |
Reliability (background) | Background operations of the app should work all the time - no silent failures |
Clarity | I want it to be easy to understand what the app is telling me, and what actions I should take. |
Usability | It should be easy to do what I want to do in the app without too much thought. |
Privacy | My personal data should not be exposed without my consent |
Security | The app should not expose me to any source of harm |
Trust | I’m putting my trust in this app. I don’t want it undermining my confidence in it. I want it to feel like a high quality product.. |
Cost | The app should not cost me much to run & use (ideally it should be free). |
Complete data | I want most infected users to share their data (actually a specific category of “False Negatives” but important enough to pull out separately) |
...