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] UI changes to address Userlytics feedback in mobile onboarding v2 #11939

Closed
karenkliu opened this issue Sep 30, 2020 · 8 comments · Fixed by brave/brave-core#7513
Closed
Assignees
Labels
OS/Android Fixes related to Android browser functionality priority/P2 A bad problem. We might uplift this to the next planned release. QA Pass - Android ARM QA Pass - Android Tab QA/Yes release-notes/include

Comments

@karenkliu
Copy link

karenkliu commented Sep 30, 2020

Description

A round of Userlytics tests for our new mobile onboarding yielded valuable feedback and surfaced UX issues. Implement minor UI changes to fix the issues.

Design

Search engine selection screen

Some people still conflate “search engine” with “browser”. Add more explanation on the search engine selection screen of why we’re letting them pick a default search engine.

image

Smaller devices may require the SE list to scroll:

image

Link Brave Shields to Privacy Reports

People could not find their way back to the “Privacy Reports” screen - nearly everyone tried to open Brave Shields when told to return to Privacy Reports. The connection is there in their head but the UI does not support the connection. Also, once finding their way to the new tab page again, they did not notice the 3-bars Privacy Reports icon in the top right corner. We should make the link between Brave Shields and Privacy Reports much clearer.

Add a link from Brave Shields directly to the detailed Privacy Reports screen.

image

Remove 3-bars Privacy Reports icon and highlight the new stats widget during onboarding.

image

Brave Shields text

A few people mentioned “...’Ads and creepy things blocked’” made them feel wary of the website. Also, this wording is a little out-of-line with our block-trackers-first stance. We should update this to “Trackers, ads, and more blocked”

image

Bookmarking icon

Someone thought tapping Bookmark icon again would unbookmark the page; instead it took them to edit the bookmark. Let’s fulfill user’s expectations and un-bookmark the page when tapping on the Bookmark icon again.

Assets

Figma: https://www.figma.com/file/atoL4LN2kd8ILnPGwohUoV/?node-id=1253%3A0

@karenkliu karenkliu added the OS/Android Fixes related to Android browser functionality label Sep 30, 2020
@karenkliu karenkliu changed the title UI changes from Userlytics feedback in mobile onboarding v2 [Android] UI changes from Userlytics feedback in mobile onboarding v2 Sep 30, 2020
@karenkliu karenkliu changed the title [Android] UI changes from Userlytics feedback in mobile onboarding v2 [Android] UI changes to address Userlytics feedback in mobile onboarding v2 Sep 30, 2020
@deeppandya
Copy link

@karenkliu Do we have the description for most common SEs? The list we show on search engine onboarding, it depends on the region as well.

@karenkliu
Copy link
Author

@deeppandya We don't - can I get a full list of SEs so we can come up with a short description for each?

@deeppandya
Copy link

@karenkliu android currently support google, DDG, DDG lite, Qwant, Bing, StartPage, Yahoo for SE onboarding. and i have a concern regarding how the UI would look in smaller screen as individual items would ttake more space.

@karenkliu
Copy link
Author

@deeppandya For smaller screens we'll need to scroll the SE list. I'll mock it up

@anthonypkeane anthonypkeane added the priority/P2 A bad problem. We might uplift this to the next planned release. label Oct 6, 2020
@karenkliu
Copy link
Author

@deeppandya I added the search engine description text and small screen treatment.

@anthonypkeane
Copy link

@karenkliu android currently support google, DDG, DDG lite, Qwant, Bing, StartPage, Yahoo for SE onboarding. and i have a concern regarding how the UI would look in smaller screen as individual items would ttake more space.

DDG lite was removed BTW

@kjozwiak
Copy link
Member

kjozwiak commented Jan 5, 2021

Moving issue into https://github.com/brave/brave-browser/milestone/161 as brave/brave-core#7513 landed in master.

@srirambv
Copy link
Contributor

srirambv commented Feb 8, 2021

Verification passed on Samsung Tab A with Android 10 running 1.20.100 x64 build

  • Verified UI changes are as per spec
  • Verified Shields has a shortcut to view privacy report
  • Verified clicking on it opens up the privacy report page
  • Verified disabling privacy report setting removes the entry from shields
  • Verified shields doesn't contain any text wording for ’Ads and creepy things blocked’
SE Onboarding Privacy stats info Trackers & Ads blocked Data Saved Time Saved
image image image image image
Trackers & Ads blocked(Re-tour) Data Saved (Re-Tour) Time Saved (Re-Tour) View Privacy report(Shields) No view privacy report (Shields)
image image image image image

Verification passed on OnePlus 6T with Android 10 running 1.20.100 x64 build

  • Verified UI changes are as per spec
  • Verified Shields has a shortcut to view privacy report
  • Verified clicking on it opens up the privacy report page
  • Verified disabling privacy report setting removes the entry from shields
  • Verified shields doesn't contain any text wording for ’Ads and creepy things blocked’
SE Onboarding Privacy stats info Trackers & Ads blocked Data Saved Time Saved
image image image image image
Trackers & Ads blocked(Re-tour) Data Saved (Re-Tour) Time Saved (Re-Tour) View Privacy report(Shields) No view privacy report (Shields)
image image image image image

Logged follow up issues #14033, #14034

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OS/Android Fixes related to Android browser functionality priority/P2 A bad problem. We might uplift this to the next planned release. 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.

5 participants