Skip to content
This repository was archived by the owner on May 16, 2023. It is now read-only.

Allow using app without Exposure Notifications implementation #464

Open
fynngodau opened this issue Apr 19, 2021 · 20 comments
Open

Allow using app without Exposure Notifications implementation #464

fynngodau opened this issue Apr 19, 2021 · 20 comments
Assignees
Labels
enhancement New feature or request mirrored-to-jira This item is also tracked internally in JIRA

Comments

@fynngodau
Copy link
Contributor

fynngodau commented Apr 19, 2021

Current Implementation

On devices without Google Play services, the Error 3 popup keeps popping up, annoying users. On iOS devices whose iOS version does not contain the required Exposure Notifications Framework version, the app is not usable at all.

Android iOS
error3 iOS

Suggested Enhancement

In the order of work required (descending), and thereby also in the order of improvement of the app (ascending):

  1. Reword the Android popup. It is false that users without Google Play services "cannot use the Corona-Warn-App", specifically considering the possibility of checking in.
  2. Pop up Android popup less. Remove block from iOS. Nobody likes using an app that keeps popping up dialogs, and the Corona-Warn-App should be usable on iOS versions with insufficient iOS versions as well.
  3. Improve the flow. Integrate the warning with the information into onboarding, instead of allowing users to tap Enable Exposure Logging, then show a warning card on the home screen informing users of the status of the app.

Expected Benefits

  1. Users who are not using Google Play services or who don't have a sufficiently recent iOS version can use Corona-Warn-App to check in at events and locations, to query statistics regarding the current infection rates in Germany, to use the Contact Journal and to retrieve their test results.
  2. Developers who are trying out the app in an emulator without Google Play services are not annoyed.
  3. iOS users with old iOS versions can use the app like described in 1.

Internal Tracking-ID: EXPOSUREAPP-6594

@fynngodau fynngodau added the enhancement New feature or request label Apr 19, 2021
@MikeMcC399
Copy link
Contributor

MikeMcC399 commented Apr 19, 2021

@fynngodau
I would enjoy seeing this implemented, especially for the emulator environment.

Perhaps it would be better for this wishlist item to be moved to the Android repository, since the error message is completely different on Android compared to the message on some versions of iOS?

Edit: Suggestive question above re-worded based on comments below about what happens on iOS.

@fynngodau
Copy link
Contributor Author

Since it's a rather big suggestion with multiple different ideas, I imagined it would be a better fit for the wishlist repository. However if this is in fact better fit for the Android repository, somebody can of course feel free to move it there.

@jucktnich
Copy link

I think, you can't use the app on iOS 13-13.7 due to the lack of ENF v 2. So a discussion about this topic does also make sense for iOS, so the wishlist is the right place.

@Ein-Tim
Copy link
Contributor

Ein-Tim commented Apr 19, 2021

The main issue for the availability is: #443

@MikeMcC399
Copy link
Contributor

@jucktnich / @Ein-Tim

What is the error message on iOS if ENF is not available? Does the app keep popping up an error message like on Android?
https://www.coronawarn.app/en/faq/#17 is specific to Google/Android.

@jucktnich
Copy link

If the iOS version has no ENF v 2 there's an update os screen, which you can't close I think.

@Ein-Tim
Copy link
Contributor

Ein-Tim commented Apr 19, 2021

@MikeMcC399

The app shows:

You can't go any further from there

@MikeMcC399
Copy link
Contributor

Ein-Tim
Thank you very much for the iOS screen shot! That makes it clear. It seems like the problems on Android and iOS are quite different in that case.

@Ein-Tim
Copy link
Contributor

Ein-Tim commented Apr 19, 2021

Yes, I would also suggest to not mix the Android Error 3 pop up together with the availability on older devices, which is tracked in #443

@jucktnich
Copy link

jucktnich commented Apr 19, 2021

I think the reason for the two messages are pretty much the same, so I would suggest to find a same solution for both.

@fynngodau fynngodau changed the title Rework Error 3 popup Allow using app without Exposure Notifications implementation Apr 19, 2021
@fynngodau
Copy link
Contributor Author

Thanks for the comments. I added your additional points to the original comment to make the issue applicable to both iOS and Android.

@heinezen heinezen added the mirrored-to-jira This item is also tracked internally in JIRA label Apr 20, 2021
@heinezen
Copy link
Member

@fynngodau and everyone else,

I have taken all your feedback and mirrored it to Jira as ticket EXPOSUREAPP-6594. The development team and the RKI will take a look at this.


Corona-Warn-App Open Source Team

@vaubaehn
Copy link

vaubaehn commented Apr 23, 2021

@fynngodau and all - concerning Android:
Isn't the pop up dialog triggered with every API call to ENS (causing an exception)?
Imho, this is not so different from corona-warn-app/cwa-app-android#2873 , the Bluetooth-based Incompatibility. Couldn't the exception be persisted and a Google Play Services Incompatibility card be shown? I think even the texts would only need minor adjustments.
What do you think?
(just to prevent misunderstandings: I don't mean changing the Bluetooth Incompatibility card, but adding another card for people affected)
2nd edit: @fynngodau already suggested this in his OP... 💤 😴

@dsarkar
Copy link
Member

dsarkar commented Apr 24, 2021

@fynngodau
Actually you could another point in your OP:
User might want to use the check-in feature.

@Ein-Tim
Copy link
Contributor

Ein-Tim commented Apr 24, 2021

@dsarkar

This is also tracked in #443.

@fynngodau
Copy link
Contributor Author

fynngodau commented Apr 24, 2021

@dsarkar This is already included under Expected benefits and in fact one of the main points why I opened this issue:

Users who are not using Google Play services can use Corona-Warn-App to check in at events and locations […]

(Though I forgot to update this to also apply to iOS)

@dsarkar
Copy link
Member

dsarkar commented Apr 24, 2021

@fynngodau You are right! Apologies, must have skipped it!

@vaubaehn
Copy link

@fynngodau
From your OP:

Suggested Enhancement

[...]
3. Improve the flow. Integrate the warning with the information into onboarding, instead of allowing users to tap Enable Exposure Logging, then show a warning card on the home screen informing users of the status of the app.

That's now also in the mind of the devs: corona-warn-app/cwa-app-android#2995 (comment)
❤️

Let's hope there will be a more relaxed situation later, that there is enough time for them to go on on that issue.

@MikeMcC399
Copy link
Contributor

@vaubaehn

Thanks for the pointer to PR corona-warn-app/cwa-app-android#2995.

  • I was able to run the pre-release 2.1 app without getting any errors on a device with ENS available, provided I did not try to activate exposure logging.
  • On a Pixel 3a emulator with no Google Play services installed, I get a warning
    "Update Google Play services
    CWA TEST won't run unless you update Google Play services." If I tap on the notification, the app opens and the functions, apart from exposure logging seem to work. If I do not tap on the notification, the app just appears with a header and nothing below on the screen.

That is a good step forward. It could be made more user-friendly though if the app is going to be supported in future in an environment without Google Play services.

@fynngodau
Copy link
Contributor Author

fynngodau commented Apr 30, 2021

@vaubaehn Thanks for linking the PR, it appears to implements my suggestion number 2 for Android ("Pop up Android popup less").

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request mirrored-to-jira This item is also tracked internally in JIRA
Projects
None yet
Development

No branches or pull requests

8 participants