MVP1 Onboarding - Testing vs. Figma Designs

A test of the MVP1 Onboarding flows. This test report covers:

Deviations from the Figma designs that I think are problems
Other points I believe are problems
Deviations from the Figma design that I think are inconsequential and/or actually improvements.

At the time of testing, the onboarding section looked like this.

Observed screenshots as follows. (the initial splash screen also shows, but I failed to capture it. It seemed to match the Figma design well.

These are categorized into

”Welcome to PathCheck”

“Terms of Use” screen

“Notifications” screen

“Allow Location Access” screen

“Allow Location Access” pop-up

App name does not match (both are wrong! - should be PathCheck or PathCheck GPS) - SAF-681 existing bug
Pop-up text does not match (this is just a standard difference between Android & iOS)

“Auto Start disabled” pop-up

Missing from Figma.
But should only occur on certain phones (e.g. Redmi), should not appear on Moto G7 phone - SAF-718 raised

For review with Design team (my personal view is that the ones that matter are the ones in bold below).

Different background on language button
Text and circle are much lower in screen than design
Heading font size is much larger & bolder
Text only just fits on screen - likely an issue for smaller devices
“Continue” button is much lower on the screen than other buttons in onboarding.

Bugs to be fixed:

Considering the process from a user perspective, rather than simply comparing to the design, concerns as follows (for discussion with Design).

Most significant: is it correct to present the full Terms to the user during onboarding, and asking them to confirm they have read them? As a point of Comparison the Italian COVID app (Immuni) requires that you confirm you have read a very short Privacy statement (6 or so short key points). Presenting a full, verbose set of terms, and asking the user to declare they have read them seems deeply misaligned with our approach on consent, where we try to lay out as clearly & simply as possible what the user is consenting to. Can we simplify this so that users actually have a chance of reading & understanding what they are signing up to?
- (I know we have been through this with Legal once before. But with direct experience now of other COVID apps not presenting verbose Terms to users, perhaps we can revisit? Is this somethign we have looked at in our user testing?)
On Terms of Use screen “Continue” button is much lower on the screen than other buttons in onboarding. While there is no Figma design, this seems inconsistent, hence probably should be fixed to be consistent with other buttons.

Pop-up text for “Disable Auto Start” is inaccurate: "PathCheck needs to be able to auto start to privately save the places you visit". This is simply not true. What may be true, on some devices, is that it needs to auto start to reliably save the places you visit (else data will be lost after a restart). (I did mention this in passing in SAF-718, but it’s not the key thrust of that bug report, so I should raise separately to get this addressed).

Get review comments from Design Team, update article, and raise further bugs as required.

Specific items for review by Design:

5 points in Amber in “Follow-ups from above”. Do they agree the 3 bold items are bugs, and the other 2 are not?
3 points in “other points for discussion”. Do they agree that these should also be raised as bugs to make further product changes?
Do design want to make any updates to Figma in light of the above?