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

Reduce length of welcome experience #12680

Closed
karenkliu opened this issue Nov 12, 2020 · 14 comments
Closed

Reduce length of welcome experience #12680

karenkliu opened this issue Nov 12, 2020 · 14 comments
Labels
closed/stale Issue is no longer relevant, perhaps because the feature it refers to has been deprecated. OS/Desktop

Comments

@karenkliu
Copy link

karenkliu commented Nov 12, 2020

Description

We need to put import on the first screen, update the copy, and reduce length of onboarding to maximize user completion.

Design for Windows, macOS, and Linux

The browser then launches with the welcome experience with improved ordering and consistent visuals.

2021-08-31 17-33-16 2021-08-31 17_34_40

"privacy preserving product analytics" links to https://brave.com/privacy-preserving-product-analytics-p3a/
"Disable" links to brave://settings/privacy

Assets

Figma: https://www.figma.com/file/MFHpcXJMg2RUQpUJMAZZ4R/?node-id=2101%3A405

@karenkliu
Copy link
Author

@aekeus or @keur Can you advise if the above designs are feasible?

@simonhong
Copy link
Member

AFAIK, making default with installer is difficult on Windows.
Because of this, I assume chrome download page also doesn't have make default checkbox.
Needs more advice from @bsclifton

@diracdeltas
Copy link
Member

@karenkliu if a user doesn't download Brave from the download page (ex: they're directly sent a link to the installer, or they install it from github/etc.), will Brave behave as if none of those checkboxes were set?

@rebron rebron added OS/Windows QA/Yes release-notes/include priority/P3 The next thing for us to work on. It'll ride the trains. labels Nov 16, 2020
@rebron rebron changed the title [Windows] Set default browser, antifraud referral confirmation check, welcome experience updates set default browser, antifraud referral confirmation check, welcome experience updates Nov 16, 2020
@diracdeltas diracdeltas added the needs-discussion Although the issue is clear, we haven't yet reached a decision about the right solution. label Nov 16, 2020
@diracdeltas
Copy link
Member

diracdeltas commented Nov 16, 2020

given my comment above, i don't think we should remove the p3a page from onboarding because not all Windows users are guaranteed to see the download page. (we can do both this page + the existing onboarding page)

@bsclifton
Copy link
Member

bsclifton commented Nov 16, 2020

Windows doesn't have a first run welcome screen (including the make default checkbox) because Windows 10 doesn't let you change this via the code. As @simonhong found out, the download page for Chromium (similar to what is proposed above) has stats auto-checked and then that value is passed through to the mini-installer. We could do that for the antifraud checkbox, but we can't touch default browser (best we can do is present the Defaults control panel app in Windows, which lets users change their default apps)

I'd personally prefer keeping the P3A pref where it's at. Another challenge would be propagating the checkbox values on this download page to macOS (which doesn't use mini_installer; not sure if we can pass anything through to PKG or DMG). This might not be possible unless we did some really weird stuff (ex: wrote our own installer / script)

@diracdeltas
Copy link
Member

@karenkliu can we update these designs to remove the referral checkbox? my understanding is that this won't ship anyway until after the referral program is shut down in 5 days.

@diracdeltas diracdeltas changed the title set default browser, antifraud referral confirmation check, welcome experience updates set default browser, welcome experience updates Nov 18, 2020
@karenkliu
Copy link
Author

For Windows, it sounds like the download page is not a good place for these checkboxes since it can't pass the make default checkbox and the user could install Brave from somewhere other than the download.

For MacOS, we'll use the first_run dialog to show these checkboxes so there's no need to worry about passing it from the download page. The MacOS issue is here: #12679

We may have to differentiate Windows and MacOS to optimize setting Brave as the default since they treat this action differently. Unfortunately for Windows, the only improvements we can make there is shortening the welcome experience (import on first slide, etc.) and the more aggressive 'set default browser' dialog on 2nd launch: #12203

I've updated the designs above to reflect this.

@karenkliu
Copy link
Author

@PrivacyMatters Rafael wanted your input on the updated P3A text in the Brave Shields slide. WDYT?
image

@PrivacyMatters
Copy link

Hi @karenkliu I'm not certain what page the hyperlinked text leads to. But I've reviewed the section in the privacy policy over https://brave.com/privacy/browser/ and that links to
image

This is probably too long but:
"We use completely anonymised privacy preserving product analytics to understand how the browser is used to help us improve it and better match the needs of our users. We genuinely don't want to know anything about you individually and the data is anonymous. You can turn off analytics in settings, Privacy and Security"

Hope that helps

pat

@karenkliu
Copy link
Author

Thanks Pat!

The text is a bit long, here's what I got it shortened down to:
image

We really shouldn't go longer than this as it's starting to make the fine print take up a bigger block than the main message of this slide - Brave Shields.

Let's keep linking to https://brave.com/privacy-preserving-product-analytics-p3a/ as we did in the previous P3A notice since the Github wiki is kind of off-putting if you land there without being primed that the data is anonymised and Brave's reasons for collecting anonymised data.

@PrivacyMatters
Copy link

PrivacyMatters commented Nov 23, 2020

Hi Karen

Just a few comments. To me "Brave protects your privacy from Brave too" sends the wrong message .. my privacy shouldn't need protecting from Brave given the privacy position on which the browser is built and promoted. I'd suggest losing that text unless user testing shows it has meaning for average users.

The reason suggested longer text, is that the use of 'analytics' is a competitive issue (& why Apple adopt an opt-in position though Firefox adopts opt-out https://support.mozilla.org/en-US/kb/share-data-mozilla-help-improve-firefox ) ...

"We use anonymised privacy preserving product analytics to understand how the browser is used to help us improve it and make it better for our users. You can turn off analytics in settings, Privacy and Security"

Is that better?

@karenkliu
Copy link
Author

Hi Pat - yes, this works much better, thanks! I've updated the designs.

@rebron rebron assigned simonhong and unassigned simonhong Jan 25, 2021
@karenkliu
Copy link
Author

Removed Yahoo from the search engine slide.

@karenkliu karenkliu changed the title set default browser, welcome experience updates reduce length of welcome experience Jan 27, 2021
@rebron rebron added OS/Linux and removed needs-discussion Although the issue is clear, we haven't yet reached a decision about the right solution. labels Jan 27, 2021
@rebron rebron changed the title reduce length of welcome experience Reduce length of welcome experience Jun 25, 2021
@rebron rebron removed their assignment Jul 22, 2021
@rebron rebron added the closed/stale Issue is no longer relevant, perhaps because the feature it refers to has been deprecated. label Jul 26, 2022
@rebron rebron removed OS/Linux OS/macOS OS/Windows priority/P3 The next thing for us to work on. It'll ride the trains. QA/Yes release-notes/include labels Jul 26, 2022
@rebron
Copy link
Collaborator

rebron commented Jul 26, 2022

Closing as stale.

@rebron rebron closed this as completed Jul 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed/stale Issue is no longer relevant, perhaps because the feature it refers to has been deprecated. OS/Desktop
Projects
None yet
Development

No branches or pull requests

6 participants