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

Android Exposure Alerts are not Kept in Chronological Order #294

Open
SSNimnicht opened this issue Jun 30, 2020 · 2 comments
Open

Android Exposure Alerts are not Kept in Chronological Order #294

SSNimnicht opened this issue Jun 30, 2020 · 2 comments
Assignees
Labels
question Further information is requested

Comments

@SSNimnicht
Copy link

Describe the bug
On a Pixel 2 with Android OS 10 loaded with CoEpi Android commit 679cfca [0.3 (95)], I was trying out the different symptoms individually at different timestamps. When viewing the Exposure Alerts "List" Screen, I noticed the alerts were not kept in a chronological order. Note clearing alerts does not appear to correct this issue.

To Reproduce
Steps to reproduce the behavior:

  1. Create several exposure alerts at different times to be received by an Android phone.
  2. Select the Exposure Alerts button on the Home Screen.
  3. Note the Exposure Alerts on the "List" Screen are NOT in an ascending or descending chronological order. [See screenshots.]

Expected behavior
To be consistent with most notification applications, the exposure alerts should display in chronological order with the most recent alert being at the top.

Screenshots
Reported Timestamps noted to the right of each Exposure Alert entry on the List Screen:
And_Exposure_Alerts_Top_Timed

And_Exposure_Alerts_Bottom_Timed

@ivnsch ivnsch self-assigned this Jul 1, 2020
@ivnsch ivnsch added this to the 0.3 milestone Jul 1, 2020
@ivnsch
Copy link
Collaborator

ivnsch commented Jul 1, 2020

They're in chronological order. The report timestamp is not considered (only contact time).

Would this be solved by improving the timestamp's UX? #288

@ivnsch ivnsch removed their assignment Jul 1, 2020
@ivnsch ivnsch removed this from the 0.3 milestone Jul 1, 2020
@ivnsch ivnsch added the question Further information is requested label Jul 1, 2020
@SSNimnicht
Copy link
Author

@i-schuetz Something to consider regarding the Exposure List Screen: Currently the new (and better yet unread) exposure alerts do not have a unique indication, so new and old exposure alerts intermingle. From a user's point of view, they will most likely go to the top of the list looking for the newest entry, but currently they will not necessarily see the newest entry. This could confuse the user or lead them to believe the application is itself confused. While many people may 'archive' old exposures, I myself wouldn't without knowing I could revisit those archived entries later and the app doesn't explain that process (if it possible). So my list could get VERY long and annoy me VERY much trying to find new exposures versus old exposures.

Depending on the timestamp UX solution, it may help with this chronological order issue. I guess the question to ask is this: "For the Exposure Alert List Screen, is the more important timestamp for conveying a symptomatic encounter when the exposure happened or when the symptoms were reported?"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

5 participants