European Version / remove Germany-specifics #110

Open
opened 1 year ago by hex · 9 comments
hex commented 1 year ago

I'm a huge fan of this app and prefer it over the solution suggested by my local government. Let's think about what would be necessary to make this app easier to use and propagate in other areas (that have a compatible system).

  • Remove "Germany" from the name
  • Replace RKI-statistics with europe-wide data (global data?)
  • The Guidelines (wash hands,..) currently suggest keeping a distance of 1.5 meters. This is the german suggestion (e.g. Austria currently suggests >=2 meters) and should be more general. ECDC doesn't mention the exact distance.
  • Support more languages (current list, upstream issue)
  • Make the TAN the prefered way to enter a test result as it's the one that is supported transnationally (list of supported countries)

This could be a seperate/additional build because Germans probably want to keep their specific features.

Related upstream issues: global release, test results from other countries

I'm a huge fan of this app and prefer it over the solution suggested by my local government. Let's think about what would be necessary to make this app easier to use and propagate in other areas (that have a [compatible system](https://www.coronawarn.app/en/faq/#interoperability_countries)). * Remove "Germany" from the name * Replace RKI-statistics with europe-wide data (global data?) * The Guidelines (wash hands,..) currently suggest keeping a distance of 1.5 meters. This is the german suggestion (e.g. Austria currently suggests >=2 meters) and should be more general. [ECDC](https://www.ecdc.europa.eu/en/covid-19/prevention-and-control/protect-yourself) doesn't mention the exact distance. * Support more languages ([current list](https://www.coronawarn.app/de/faq/#available_languages), [upstream issue](https://github.com/corona-warn-app/cwa-wishlist/issues/136)) * Make the TAN the prefered way to enter a test result as it's the one that is supported transnationally ([list of supported countries](https://www.coronawarn.app/en/faq/#test_in_other_country)) This could be a seperate/additional build because Germans probably want to keep their specific features. Related upstream issues: [global release](https://github.com/corona-warn-app/cwa-wishlist/issues/46), [test results from other countries](https://github.com/corona-warn-app/cwa-wishlist/issues/433)
Bubu commented 1 year ago
Owner

Thanks for gathering the information in this issue, we also made a post about this on mastodon: https://social.tchncs.de/@CCTG/105971693774428236

That said this is going to increase our maintenance and support burden by quite a large amount, which is something that is just not going to happen at this point without more people getting involved in maintaining the app.

Thanks for gathering the information in this issue, we also made a post about this on mastodon: https://social.tchncs.de/@CCTG/105971693774428236 That said this is going to increase our maintenance and support burden by quite a large amount, which is something that is just not going to happen at this point without more people getting involved in maintaining the app.
Bubu added the
help wanted
enhancement
labels 1 year ago
Owner

Thinking about what we can do to make our application more attractive to users outside of Germany is a great idea.

I'll go over your thoughts one-by-one to consider what we can realistically do within the scope of our project.

  • Replace RKI-statistics with europe-wide data (global data?)

A setting to choose a different data source would generally be a great addition, but there are already other apps to show COVID statistics that are probably better fit for this purpose, and as mentioned this is probably not something we'd want to be required to keep in sync with upstream changes (→ increases maintenance efforts).

However an option to hide statistics, intended for users to whom they are not relevant, might be somewhat feasible.

  • Support more languages

We could probably set up a Weblate to do this without much effort, provided that we can prohibit translators from editing languages that are already available upstream.

Ideally, of course, we could share our additional translations with upstream, however they don't seem very keen on adding community-provided translations.

  • The Guidelines (wash hands,..) currently suggest keeping a distance of 1.5 meters.

I understand that other countries might provide slightly different advice here, but I'm not sure whether the difference really is that important.

  • Make the TAN the prefered way to enter a test result

What I think would be a realistic change, for upstream even, would be to modify the dispatcher screen ("Retrieve Test Result") such that it indicates that TANs are supported abroad, and that QR code scans are only possible when a German test is used.

I've opened this whishlist issue with my ideas: https://github.com/corona-warn-app/cwa-wishlist/issues/439

Specifically, we could "indicate in which countries the according methods are available through flags on the dispatcher screen itself" even if upstream doesn't decide to do that, as it would only require changing a few layout resources.

On that note, upstream is going to add the international TAN hotline to the app in version 2.1 according to this iOS changelog PR (thanks to the community slack for pointing this out).

  • Remove "Germany" from the name

I'm conflicted here: I don't think we need a different build flavor just to give it another name, but I also don't think we should change the name. Admittely, the current name is not too catchy and we didn't really think about the possibility of using the app in other countries when coming up with it, but the acronym CCTG has become rather familiar to the community.

Thinking about what we can do to make our application more attractive to users outside of Germany is a great idea. I'll go over your thoughts one-by-one to consider what we can realistically do within the scope of our project. > * Replace RKI-statistics with europe-wide data (global data?) A setting to choose a different data source would generally be a great addition, but there are already other apps to show COVID statistics that are probably better fit for this purpose, and as mentioned this is probably not something we'd want to be required to keep in sync with upstream changes (→ increases maintenance efforts). However an option to hide statistics, intended for users to whom they are not relevant, might be somewhat feasible. > * Support more languages We could probably set up a Weblate to do this without much effort, provided that we can prohibit translators from editing languages that are already available upstream. Ideally, of course, we could share our additional translations with upstream, however they [don't seem very keen on adding community-provided translations](https://github.com/corona-warn-app/cwa-app-android/issues/1982#event-4143834147). > * The Guidelines (wash hands,..) currently suggest keeping a distance of 1.5 meters. I understand that other countries might provide slightly different advice here, but I'm not sure whether the difference really is that important. > * Make the TAN the prefered way to enter a test result What I think would be a realistic change, for upstream even, would be to modify the dispatcher screen ("Retrieve Test Result") such that it indicates that TANs are supported abroad, and that QR code scans are only possible when a German test is used. I've opened this whishlist issue with my ideas: https://github.com/corona-warn-app/cwa-wishlist/issues/439 Specifically, we could "indicate in which countries the according methods are available through flags on the dispatcher screen itself" even if upstream doesn't decide to do that, as it would only require changing a few layout resources. On that note, upstream is going to add the international TAN hotline to the app in version 2.1 according to [this iOS changelog PR](https://github.com/corona-warn-app/cwa-app-ios/pull/2370) (thanks to the community slack for pointing this out). > * Remove "Germany" from the name I'm conflicted here: I don't think we need a different build flavor just to give it another name, but I also don't think we should change the name. Admittely, the current name is not too catchy and we didn't really think about the possibility of using the app in other countries when coming up with it, but the acronym CCTG has become rather familiar to the community.
Owner

Small bummer on internationalization efforts: rapid tests results are only going to be able to be shared among German app users, it seems: https://github.com/corona-warn-app/cwa-app-android/pull/2840/files#diff-669db4487acd70831051888f87d6e297b903c2d6f273b675aa068ac688d9e765R23

Small bummer on internationalization efforts: rapid tests results are only going to be able to be shared among German app users, it seems: https://github.com/corona-warn-app/cwa-app-android/pull/2840/files#diff-669db4487acd70831051888f87d6e297b903c2d6f273b675aa068ac688d9e765R23
Bubu commented 1 year ago
Owner

huh, what's the reason behind this though 🤔?

huh, what's the reason behind this though :thinking:?
Owner

Maybe they haven't reached a common agreement with the other EU nations that they want to do that…

Additionally, QR code check-ins are not federated anywhere either :(

Maybe they haven't reached a common agreement with the other EU nations that they want to do that… Additionally, QR code check-ins are not federated anywhere either :(
Owner

Here's a bit of good news: app shows international phone numbers from version 2.1 onwards.

Here's a bit of good news: app shows international phone numbers from version 2.1 onwards.

if you want to get in contact with the folks making the Dutch app, I can make that happen. But there are all sorts of differences in approaches that would have to be sorted out.

if you want to get in contact with the folks making the Dutch app, I can make that happen. But there are all sorts of differences in approaches that would have to be sorted out.
Bubu commented 1 year ago
Owner

@jfinkhaeuser not familiar with the dutch app/app landscape. Is there a microG based variant already? (Switzerland has one, I don't think I know any others.

Apart from that what are you expecations of working with the NL app develoopers, what is the goal here? :-)

But there are all sorts of differences in approaches that would have to be sorted out.

Could you add some context here?

@jfinkhaeuser not familiar with the dutch app/app landscape. Is there a microG based variant already? (Switzerland has one, I don't think I know any others. Apart from that what are you expecations of working with the NL app develoopers, what is the goal here? :-) > But there are all sorts of differences in approaches that would have to be sorted out. Could you add some context here?

Well, I have no goal. I saw the suggestion that a European app be made, and figured that pooling resources with developers from other countries would be the best way to go. Beyond that, I have no preferences.

The last time I spoke with someone from the official Dutch app, they said it doesn't use Google's services, but implements the improved version of the same approach. Apparently there were some addendums and fixes published by the paper authors, but Google didn't implement them. I'd have to ask details.

But of course this only really makes sense if the intent exists to collaborate here, which I'm not sure there is, reading this thread.

Well, I have no goal. I saw the suggestion that a European app be made, and figured that pooling resources with developers from other countries would be the best way to go. Beyond that, I have no preferences. The last time I spoke with someone from the official Dutch app, they said it doesn't use Google's services, but implements the improved version of the same approach. Apparently there were some addendums and fixes published by the paper authors, but Google didn't implement them. I'd have to ask details. But of course this only really makes sense if the intent exists to collaborate here, which I'm not sure there is, reading this thread.
Sign in to join this conversation.
No Milestone
No Assignees
4 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.