co-epi / app-android Goto Github PK

Add new Dark/Light Backgrounds for Fragments. See figma for assets and which background each fragment has.

See Figma for details.

Note - may tweak the background rectangle 'texture' design, so can be built in the interim to focus on buttons etc.

When a progress indicator is visible, it should not be possible to interact with the view behind it.

see Figma for details

I want to tweak this text but Figma is using a font I don't have so please tag me in the PR for these screens and I'll plan to edit it there.

See Figma for latest

(circles will include graphic visuals)

Once users select symptoms, prompt them to pick a date when each of the selected symptoms started.

Symptom inputs need to be mapped to severity and encoded in the message to the backend.

Mapping should be:

• 3 states for Fever: no fever (<98.6); mild (<100.5); fever (>100.6)
• 3 states for Cough: no cough, wet cough, dry cough
• 1 state for breathlessness - (yes/no)

Submit buttons should have rounded corners. See figma for details.

See Figma for details.

Look into what needs to happen to make the app accessible following Android best practices

• Delete too old (3-4 weeks?) CENs and alerts regularly from DB

See Figma for details.

https://coepi.slack.com/archives/C011VEHP9SM/p1588040017174300

Update to match new UX in Figma.

See #59 (comment) for more details.

Quote:

Since this fixes the problem quickly, let's merge it, but we should investigate a proper solution, as android:extractNativeLibs is not ideal.

Paths of investigation:

• Page alignment is apparently controlled by passing a flag -p to zipalign. See if this can be configured in the build gradle file.
• Contact the AppCenter support. I overflew the build settings and didn't see anything that can be used. May have missed something.

See Figma for details.

Buttons should have drop shadows per figma.

see Figma for details.

Describe the bug
If cellular Network is disabled one gets and Error message NOT installed and the cellular network is a must for CoEpi to work https://youtu.be/-x6d2T6Uwu4
To Reproduce
Please help post a comment if anybody is able to reproduce this Error during android OS 8.1 Oreo with Wifi Only connection enabled and Mobile Network Disabled on the phone

Describe the bug
On the BreathlessViewModel, there appears to be a Type Mismatch error in the onSelected function

To Reproduce
Steps to reproduce the behavior:

1. Try to build
2. Failure, and error should be in BreathlessViewModel (ui->symptoms->breathless)

Additional context
Current Development build of app-android is failing, this should be the cause of the crash

When a report is matched, the contact exposure system notification shows, but the alert doesn't show up on the home screen or in the exposure alerts page.

The TCN library now reports estimated distances. When storing a TCN, we should store the average and minimum distance observed for each one, and if there's later an exposure match, display the estimated distance for the observed TCN.

When displaying an exposure match, symptom information in the report should be displayed along with the timestamp of the match.

Is your feature request related to a problem? Please describe.
I don't use Google Play Store and instead use FDroid for Free Software only apps. I'd like to test this app, but cannot do it currently.

Describe the solution you'd like
You should publish this app on https://f-droid.org/

Describe alternatives you've considered
Or a less elegant option would be provide a direct apk download.

Additional context
F-Droid is an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform. The client makes it easy to browse, install, and keep track of updates on your device.

I tried to be a beta tester, but my phone is Android 5.1 (API level 21) and thus I cannot run the app.

Here is an analysis of what should still be possible even in older phones, from the tracing app being developed by colleagues of mine at EPFL: DP-3T/dp3t-sdk-android#16

Problem: With turbulent changes in this rep, it's unclear for new users/testers how to build the app and which branch to use.

Solution* Add two entries to the README for this repo:

• A pointer to "Getting Started" a build instructions doc (and might as well add testing instructions, too). (Mark Ingle has written a build doc for iOS already).
• A (dynamically changing?) note in the README abut which repo branch to build from.

see Figma for details

I'm using the version tagged as Android 0.2 build 83 in MS App Center, and on the app home screen it reports its version as 0.2 (1).

If the app detects an exposure match in the background, issue a notification.

After successfully reporting symptoms, the Android app should return to the home screen like the iOS app does.

Implement what's missing from the 0.1 Figma spec in the app. Confirm first with UX that it's still required. See if there are other needed improvements or things that are missing in Figma.

See Figma for details.

see figma for details.

Hi Dana and Scott,

Hope you’re well.

I have a team of highly skilled developers in Native Mobile on iOS and Android, as well as Backend and System Architects waiting in the wings ready to build out a Contact Tracer system.

Do you have some time to talk today or tomorrow? I’m on PST. My email is Rnorback [@] gmail.com.

Best,
Rob Norback

Goal: we want to add a screen where, at the end of the symptom workflow (after any severity workflow is done), to ask users what the earliest day of the symptom onset was?

Use same design as the 'how many days of cough'/fever screen, but we'll adjust the text depending on whether there is a single symptom submitted, or multiple.

Describe the bug
On the Symptom Report screen when selecting certain options in the symptoms list the app crashes. These options include:

• I don't have any symptoms today
• Muscle aches
• Loss of smell or taste
• Diarrhea
• Runny nose
• I have symptoms that are not on the list

To Reproduce
Steps to reproduce the behavior:

1. Navigate to Symptom Report screen
2. Select any of the options mentioned above
3. Click submit
4. Observe crash

See Figma for latest

(3.2 scale may change)

Once the new UX screens are implemented, we need to implement a data model for storing their results and then wiring that up to the new v0.4 cloud API backend.

If more than one TCN matches from a given TCK, we should estimate and display the duration of the contact.

Just happened to run the new UI, some issues:

• The button shadows are missing https://www.figma.com/file/W488uiXhnllYTkMcsBvAcX/CoEpi?node-id=21628%3A30070
• The submit button should have round corners.
• The buttons feel a bit too close together and/or small. Can imagine people mis-tapping them (more if sick).
• It should not be possible to select "No symptoms" and any of the other buttons at the same time.
• The vector background is missing. I think we can reuse the one from the thanks screen.
• Do we want to keep the green notification with "Symptoms submitted"? Probably it's redundant now?
• The buttons/items should have probably ripple effect (this is standard, but maybe confirm with UX).

Update the splash screen to match the new theme and layout in the UX

After entering a number in a edit field, the keyboard is still on the screen going to the next item, which can cause visual artifacts. When leaving a screen that has an input field, we should make sure the keyboard is closed.

Screenshot below taken on a Galaxy S9, 2220x1080.

We added functionality to Rust to support struct and callbacks in FFI, for iOS: https://github.com/Co-Epi/app-backend-rust/blob/master/src/ios/ffi_for_sanity_tests.rs

Specifically:

• Passing struct to Rust as a parameter.
• Receiving struct from Rust as return value.
• Passing callback as a parameter.
• Passing callback and triggering it.

These are the corresponding Unit Tests in the iOS app:
Co-Epi/app-ios@5832b0c

One the JNI interface is ready (issue), port the Unit Tests to Android.

@yibter you can do the Rust issue too, if you want.

Edit: I'd add the current string/JSON experiment to these tests.

We should update the home screen to use a recycler view. Note that it will need to support the notification badges used on the exposure card.

Please link 'how is my data used' on onboarding screen to https://www.coepi.org/privacy/ for now

Once Co-Epi/coepi-backend-aws#6 is complete, transition the app to use it.

Integrate the App Backend Rust project...
https://github.com/Co-Epi/app-backend-rust

Mimic the iOS Rust Integration as much as possible...
https://github.com/Co-Epi/app-ios/tree/feature/rust-integration

Adding Native Code to Android...
https://developer.android.com/studio/projects/add-native-code

Cargo NDK for building Android libs...
https://docs.rs/crate/cargo-ndk/0.2.0

Older, but pretty good example from Mozilla using Rust in Android...
https://mozilla.github.io/firefox-browser-architecture/experiments/2017-09-21-rust-on-android.html

Interesting decentralized native package dependency manager
https://github.com/google/cdep

Native Dependencies in Android Studio 4.0 (beta)
https://android-developers.googleblog.com/2020/02/native-dependencies-in-android-studio-40.html