Skip to content
Snippets Groups Projects
user avatar
Oliver Zimmerman authored
* initial commit of new fragment for symptom screen

* Added relevant strings for symptom screen. Started editing xml of initial symptom screen

* Addded 3 selection options within symptom screen

* button id name change to something more relevant

* ID changes to be something more relevant to symptom scenerio.

* Implemented symptom initial screen logic. Temporary nav for testing.

* CircleCI formatting

* Adapted interoperability test provided by apopov

* Added accessibilty announcement on resume, fixed navigation for main page

* circleCI indentation fix

* removed ar & ru and updated default strings

* Adaption to ViewModel logic. Not yet complete

Adaption to ViewModel logic, attempting to align with implementation done with some interoporibility tasks: reusable layout files, etc.

* More ViewModel transformation additions

* revert nav from test. Circle CI formatting changes

* Update SubmissionSymptomIntroductionFragment.kt

* Removed old fragment based test

* Will implement navigation during marry session.

* Update SubmissionViewModel.kt

* Calendar button selection screen + required strings

* Custom calendar view

* Accessibility improved

* introduced data types for symptoms

* represent date by long in millis

* new TransmissionRiskVector

* Constants and formatting

* Naming changes requested

* Better event naming

* Update fragment_submission_symptom_intro.xml

* Finishing calendar implementation - still need to implement calendar widget

Surrounding calendar submission UI - minus calednar widget
Necessary strings

* Merged introduction and calendar screen.

Created calendar fragment screen,
Finished calendar XML view
Added required entries for choices in SubmissionViewModel
Adjusted Formatters for button selection.
Changed nav graph.

* + todo

* CircleCI code style changes

* EXPERT STUFF

* Latest push for marry session

* replaced transaction risk vector

* update textcolor on symptom indication change

* update buttons by code

* code formatting

* Added logic for Negative and No Information buttons and adjusted xml view to be more aligned with design

Added logic for Negative and No Information buttons and adjusted xml view to be more aligned with design

* disable next button when state is null.

* + readability

* Calendar screen logic adapted for button selection

* extracted domain logic from prototype and from transaction

* - not used events

* joint improvements

* removed unused events

* Calendar unsetSelection added

* detekt rules changed and formatting

* - calendar view refactor: CalendarCalculator singleton introduced for batter testing capacity
- unit tests added

* detekt issues

* Colors and styles cleared

* fixed strings

* maintained unit tests

* adopted changes from main nav graph to device for testers nav graph

* reverted comment

* made start of symptoms nullable

* tests

* Adjusted navigation, fixed dark theme

* Update Project.xml

* use of postValue() in SubmissionViewModel.kt

* Added direction in tester nav graph

* improvements required by review

* moving companion

* moving companion

* moving companion

* fixed issues from partner review

* fixed issues from partner review

* fixed issues from partner review

* fixed issues from partner review

* fixed issues from partner review

* using utc

* edge case tests

* made inner class

* Refactored Symptoms Class Name (+data class)

* Change SubmissionViewModel scope to ensure that the same viewmodel is used to store submission data.

* extracted null check + log

Co-authored-by: default avatarLuka Harambasic <luka.harambasic@sap.com>
Co-authored-by: default avatarchris-cwa <chris.cwa.sap@gmail.com>
Co-authored-by: default avatarAlexander Alferov <a.alferov@sap.com>
Co-authored-by: default avatarharambasicluka <64483219+harambasicluka@users.noreply.github.com>
Co-authored-by: default avatarMatthias Urhahn <darken@darken.eu>
Co-authored-by: default avatarMatthias Urhahn <matthias.urhahn@sap.com>
8c7e0501
History

Corona Warn App - Android

DevelopmentDocumentationContributeSupportChangelogLicensing

The goal of this project is to develop the official Corona-Warn-App for Germany based on the exposure notification API from Apple and Google. The apps (for both iOS and Android) use Bluetooth technology to exchange anonymous encrypted data with other mobile phones (on which the app is also installed) in the vicinity of an app user's phone. The data is stored locally on each user's device, preventing authorities or other parties from accessing or controlling the data. This repository contains the native Android implementation of the Corona-Warn-App. Visit our FAQ page for more information and common issues

Development

Known Issues

  • The Exposure Notification API is going to block you from successfully testing the Application unless you are whitelisted inside GMS; Shoutout to @pocmo for working on a demo mode to test unreleased app versions in advance without whitelisting (issue #321), if you want to contribute you can reach out here for the time being - thank you!
  • The Storage is currently based on Encrypted Shared Preferences and SQL Cipher (SQLite) - this could change in the future
  • Test Coverage is generally low and needs to be improved. We appreciate your help here!
  • In General every TODO comment within the code or the documentation can be regarded as an issue. You are free to tackle the TODOs anytime!
  • We are aware of the Play Store Limitations of GMS.
  • Without your own server instance (e.g. a local Docker setup), you will not be able to test the Application. For help, please refer to the server implementation.
  • Strings including translations are handled separately, for suggestions / findings please have a look at issue #332

Architecture & Documentation

The full documentation for the Corona-Warn-App is in the cwa-documentation repository. The documentation repository contains technical documents, architecture information, UI/UX specifications, and whitepapers related to this implementation.

Support & Feedback

The following channels are available for discussions, feedback, and support requests:

Type Channel
General Discussion
Feature Requests
Concept Feedback
Android App Issue
Backend Issue
Other Requests

How to Contribute

Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our Contribution Guidelines. By participating in this project, you agree to abide by its Code of Conduct at all times.

Contributors

The German government has asked SAP and Deutsche Telekom to develop the Corona-Warn-App for Germany as open source software. Deutsche Telekom is providing the network and mobile technology and will operate and run the backend for the app in a safe, scalable and stable manner. SAP is responsible for the app development, its framework and the underlying platform. Therefore, development teams of SAP and Deutsche Telekom are contributing to this project. At the same time our commitment to open source means that we are enabling -in fact encouraging- all interested parties to contribute and become part of its developer community.

Repositories

Repository Description
cwa-documentation Project overview, general documentation, and white papers.
cwa-wishlist Community feature requests.
cwa-app-ios Native iOS app using the Apple/Google exposure notification API.
cwa-app-android Native Android app using the Apple/Google exposure notification API.
cwa-server Backend implementation for the Apple/Google exposure notification API.
cwa-verification-server Backend implementation of the verification process.

Licensing

Copyright (c) 2020 SAP SE or an SAP affiliate company.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License.

You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0.

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the LICENSE for the specific language governing permissions and limitations under the License.