Currently, users can find the latest information (e.g. about problems) only through the FAQ.
So f.e. if users under iOS 13.6 wonder why the App is not working, they have to go to the FAQ and find this answer.
If the App would just show an info box on the main screen that this problem is known and solved with iOS 13.6.1, I assume that more users would see this and don't just say the App is not working but upgrade their iOS version.
I think it would be nice if users would be able to see more informations inside the App via f.e. an info box, etc.
The users should be able to close the box after they read it.
It would be much easier for users to get important information, and it could be personalized better (e.g. not showing Android information to someone using iOS)
Internal Tracking ID: EXPOSUREAPP-2331
Hello @Ein-Tim,
thanks for sharing your idea! I personally really like it. There is a thread about a similar topic, I like to link here: https://github.com/corona-warn-app/cwa-wishlist/issues/134 this was more about a status board, but similar in some way that both issues are describing ways to inform the users about the latest changes or important information in general.
I will transfer this issue to JIRA so that it gets in the hands of the right people.
Thanks you,
LMM
Corona-Warn-App Open Source Team
Thank you! @GPclips
And thanks for all your quick and nice replies 馃憤
Related issues:
I also really like @vaubaehn's idea here:
Yes, my idea was going into a quite similar direction, I drew a primitive sketch about it -> here, but didn't take time yet for polishing and putting it into the wishlist repo.
In short, I describe a Concept On Viewing important Reliability Information of Device = COVirD (to be pronounced: co-weird) ;)
Sounds like a big thing to implement, but if some very small basics are set up first, it may be extended release by release (quite modular). So, if an error / exception / incompatibility would be detected, a card would show up, and link to in-app information or external FAQ. The 'root' card in main screen could provide genral information, if 'everything works fine' with CWA, and in case of problems it could be the starting point for finding information and solutions.
I second this and like to add something:
pls explain the actual meaning of Timestamps of a Matched Key in "Exposure Checks"-Detail Screen and tell the users, what it really is and what not. Because so many people believe that this timestamp will reflect the timestamp of the concrete Contact! I saw this in several discussions and a simple text label could avoid mis-interpretation here (and save time for those people that have to explain it several times).
see also https://github.com/corona-warn-app/cwa-app-ios/issues/1245 for more information. Thx :)
Something what makes me really sad (we also talked in the community slack about this: https://covidapps.slack.com/archives/C0194ML0MLN/p1608214559132100):
With 1.9.1 CWA updated to version 2 of the ENF.
With that version it is possible that encounters are shown in the log but not in the App anymore. Also after the update user will see a drop in encounters: https://github.com/corona-warn-app/cwa-app-ios/issues/1703. This is very confusing and in combination with the matches shown in the Log, many users will think that this is a bug.
There neither 2 new FAQ entries nor a blog post helps, since the normal user doesn't know about this (since the App does not inform the user that Blog and FAQ does exist... very sad)
@Ein-Tim
There neither 2 new FAQ entries nor a blog post helps, since the normal user doesn't know about this (since the App does not inform the user that Blog and FAQ does exist... very sad)
The FAQ section in the app links to the site of The Federal Government through main_about_link
https://www.bundesregierung.de/corona-warn-app-faq-englisch
https://www.bundesregierung.de/corona-warn-app-faq
The German language page:
So, in summary, the German language page does give the user a route to the Blog and FAQs, even though it is indirect.
The English language page of the Federal Government (https://www.bundesregierung.de/corona-warn-app-faq-englisch) needs some significant improvement. Perhaps the Open Source Team has some direct contact (or indirect contact through RKI) to request some improvement to the English language page? I did try a couple of weeks ago by using the contact form on this site, but I never got any response.
I will add this specifically to the GitHub website issues so it can be passed one-to-one on to the other website owners of the Bundesregierung.
@MikeMcC399
So, in summary, the German language page does give the user a route to the Blog and FAQs, even though it is indirect.
Yes, but be honest: Will the normal user find this? No...
I will add this specifically to the GitHub website issues so it can be passed one-to-one on to the other website owners of the Bundesregierung.
Thank you!
@Ein-Tim
So, in summary, the German language page does give the user a route to the Blog and FAQs, even though it is indirect.
Yes, but be honest: Will the normal user find this? No...
I share your concerns that the level of redirection to find information is too deep.
I will add this specifically to the GitHub website issues so it can be passed one-to-one on to the other website owners of the Bundesregierung.
I have created https://github.com/corona-warn-app/cwa-website/issues/711 now. At the least the available information should be helpful and current.
(BTW: I'm still not seeing CWA 1.9.1 in the Google Play Store.)
Most helpful comment
Something what makes me really sad (we also talked in the community slack about this: https://covidapps.slack.com/archives/C0194ML0MLN/p1608214559132100):
With 1.9.1 CWA updated to version 2 of the ENF.
With that version it is possible that encounters are shown in the log but not in the App anymore. Also after the update user will see a drop in encounters: https://github.com/corona-warn-app/cwa-app-ios/issues/1703. This is very confusing and in combination with the matches shown in the Log, many users will think that this is a bug.
There neither 2 new FAQ entries nor a blog post helps, since the normal user doesn't know about this (since the App does not inform the user that Blog and FAQ does exist... very sad)