Brave-browser: set default browser, welcome experience updates

[karenkliu]

Description

We need to update the onboarding flow with:

• More aggressive pitch for set default browser for increased retention and engagement
• Reduce length of onboarding to maximize user completion

Design for Windows

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

• Replace 1st "Let's Go" slide with the import slide
• Search engine slide is 2nd
• Incorporate search engine icons into SE dropdown
• Brave Shields is 3rd
• Update P3A text on Brave Shields slide
• Brave Rewards is 4th and last
• Update search engine slide graphic
• Update Brave Rewards slide graphic with Lottie file

Keep using the same P3A link: https://brave.com/privacy-preserving-product-analytics-p3a/

Assets

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

Brave Rewards slide Lottie file:
preview: https://lottiefiles.com/share/6RkxWM
json file: https://assets3.lottiefiles.com/packages/lf20_6RkxWM.json
implementation info: http://airbnb.io/lottie/#/web

[karenkliu]

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

[simonhong]

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]

@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?

[diracdeltas]

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]

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]

@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.

[karenkliu]

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: https://github.com/brave/brave-browser/issues/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: https://github.com/brave/brave-browser/issues/12203

I've updated the designs above to reflect this.

[karenkliu]

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

[PrivacyMatters]

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

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]

Thanks Pat!

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

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]

Hi Karen

Just a few comments. To me "Brave protects your privacy from Brave too" sends the wring 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]

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