Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Android] Updates to Onboarding Welcome Screens #22946

Closed
timchilds opened this issue May 19, 2022 · 2 comments · Fixed by brave/brave-core#13405
Closed

[Android] Updates to Onboarding Welcome Screens #22946

timchilds opened this issue May 19, 2022 · 2 comments · Fixed by brave/brave-core#13405
Assignees
Labels
onboarding Front-end related to helping a new user learn about features within the browser. OS/Android Fixes related to Android browser functionality QA Pass - Android ARM QA Pass - Android Tab QA/Yes release-notes/include

Comments

@timchilds
Copy link

Product Spec:
https://docs.google.com/document/d/12Yd98rnfn6cPEowr96v4bbgwD2pbYsZw8awH10n7VPg/edit

@kjozwiak
Copy link
Member

Adding missing labels. Specifically missing the QA/Yes label.

@kjozwiak kjozwiak added QA/Yes release-notes/include onboarding Front-end related to helping a new user learn about features within the browser. labels Jun 14, 2022
@Uni-verse
Copy link
Contributor

Uni-verse commented Jun 30, 2022

Verified on Samsung GS 21 & Galaxy Tab S7 using

Brave	1.41.86 Chromium: 103.0.5060.66 (Official Build) beta (64-bit) 
Revision	20b1569438a85e631d15e83eb355e3e326e5da6f-refs/branch-heads/5060@{#1066}
OS	Android 12; Build/SP1A.210812.016
Welcome Animation
  • Animation includes initial brave logo > welcome text > set to default phase
  • UI matches the spec designs
1 2 3
screenshot-1656629751910 screenshot-1656629756081 screenshot-1656629763716
screenshot-1656699947046 screenshot-1656699954685 screenshot-1656699995605
Set Default
  • User able to select Set as default browser which will show option prompt
  • User able to select Not now
  • User able to proceed to the next onboarding screen after selecting skipping default screen
1 2
screenshot-1656628665908 screenshot-1656628677489
screenshot-1656701465146 screenshot-1656701477215
P3A
  • Checkboxes on the P3A screen are selectable and user is able to successfully complete onboarding when opting-out from P3A.
  • Confirmed P3A settings under privacy setting will reflect the selection made in the onboarding screen.
1 2 3
screenshot-1656629793987 screenshot-1656629969473 screenshot-1656630083897
screenshot-1656701485474 screenshot-1656701186870 screenshot-1656700057975
Shields
  • Confirmed shields explainer modal is displayed when user enters domain
  • Confirmed shields explainer modal is displayed when user selects result from search
  • Confirmed where trackers from Google, Facebook or Amazon include names of these companies in the modal text, otherwise only display X ads & trackers blocked.
  • Confirmed shields modal does not show up again if user opens another tab
1 2 3 4
screenshot-1656629827369 screenshot-1656630986015 screenshot-1656631277503 screenshot-1656631380472

Tablet
0

Upgraded Profile

Performed upgrade using 1.40.79 (May 29 Beta Build) -> 1.41.86

  • Verified shields explainer modal is displayed if existing profile has not entered domain or clicked on search result before upgrading.
  • Verified shields explainer modal is not displayed if existing profile has previously entered domain or clicked on search result.

@Uni-verse Uni-verse added QA/In-Progress Indicates that QA is currently in progress for that particular issue QA Pass - Android ARM QA Pass - Android Tab and removed QA/In-Progress Indicates that QA is currently in progress for that particular issue labels Jun 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
onboarding Front-end related to helping a new user learn about features within the browser. OS/Android Fixes related to Android browser functionality QA Pass - Android ARM QA Pass - Android Tab QA/Yes release-notes/include
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants