Fenix Settings Menu Experiment (Test_branch 2:Default Browser at #1 position, Control: Sync at #1 position)

[ItsDevyani]

User Story

• As a user, I want to know how I can easily set up Fenix as my default browser when I click the settings menu.

Dependencies

• Setting Menu re-design (done)
• Nimbus SDK integration with Fenix
• DS resources to write measurement plan, DS Ticket is here.
• Engineering Time

Acceptance Criteria

• Set Default Browser is the First Item on the Settings Menu (It replaces Sync)
• We can track default browser activations coming from this source full-funnel (Clicks at each step) including conversion to default.
• Nimbus SDK integration with Settings menu to enable testing on it.

Engineering notes

• Nimbus engineering docs
• This will be an A/B test for changing the card at the top of the Settings menu to "Set as default browser" (see designs)
• The control to test against will be the "Turn on Sync" card (what we currently have in release) with a "set to default" item lower down in the settings menu:

• Please sync with data science before starting this implementation to confirm the following:
  Experiment length: 35 days total, 7 day enrollment period
  Start date: Release with 89 (preferably)
  Experiment size: TBD
  A/B split: 50/50
  Channels: Release, Nightly

  • all of the Nimbus experiments should be pushed to nightly first. [...] Also, they don't need to go to beta afterwards but instead can go to production.

Probes
Should we use the same probe to track "set to default" clicks in both A and B states? Or should we create a different probe that is specifically for the new card?

• If you just have the “button_clicked” event, then Glean will handle the rest of which branch they were in

• It doesn't really matter if we have one "set to default click" probe or two. Whoever picks this up should reach out to the data science team to see what their preference is and work from there :)

Proposed probes: clicks on "Turn on sync" card (control state), clicks on "Set as default browser" card (testing state), clicks on sync pref item (testing state)

┆Issue is synchronized with this Jira Task

[ItsDevyani]

Nicole Weber is doing the design for this. We'll see 1st drafts on 3/15.

[Amejia481]

The experiment changes completely how the "turn sync UI" looks, do we have UI mocks for the multiple states on which this setting could be? They are Authenticated, LoggedOut (the one is showing) and Authentication Problems.

[ItsDevyani]

Hello Nicole, Can you please help with these additional views of the Settings menu? Thanks, Devyani

…

On Wed, Mar 24, 2021 at 2:28 PM Arturo Mejia ***@***.***> wrote: The experiment changes completely how the "turn sync UI" works, do we have UI mocks for the multiple states on which this setting could be? They are *Authenticated*, *LoggedOut* (the one is showing) and *Authentication Problems*. [image: image] <https://user-images.githubusercontent.com/773158/112385416-fc0ba680-8cc5-11eb-9ad5-21530189552a.png> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#18376 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AICH2E3QPRVI5NFPE4M2TATTFJKPPANCNFSM4YZ6F34A> .

-- Thanks, Devyani

[topotropic]

Sure, I added the logged in state (https://www.figma.com/file/w8vFnZ05xMgDPkEb9r0r35/R89?node-id=0%3A1).

@Amejia481 what auth problems do we support here and how can I reproduce them? We don't have them documented in our existing files. Thanks!

[Amejia481]

Thanks 😊
I think the only one is when users are signed in but they need to re-authenticate as the password has changed on another device.

[topotropic]

Thanks, Arturo! I added the case https://www.figma.com/file/w8vFnZ05xMgDPkEb9r0r35/R89?node-id=0%3A1

[amedyne]

Note: This ticket will be for tracking the Engineering tasks for developing Experiment Test Branch 2: Set Default Browser is the First Item on the Settings Menu (It replaces Sync) and the corresponding telemetry needed for this branch.

[mcarare]

@topotropic Should we also keep the Account preference category in order to provide some consistency for users who will be enrolled in the experiment? And also the custom user avatar (profile picture) and the yellow background for sync problems?

I've attached screenshots with these, let me know if they are ok or should I follow the mocks in Figma exactly? Thank you!

[topotropic]

Thanks, Mihai! This looks good.

[abodea]

I was able to verify that the changes mentioned above are in Fenix for more details please check the following:

• The prompt with the following text Set links from websites, emails, and messages to open automatically in Firefox. is displayed at the top replacing the Turn on Sync card.

• The Turn on Sync card moved under General with its own section.
  I was able to log in without issues and that section works as expected.
  

There are two different behaviors for the default browser:

• When Nightly is already set as the default browser
  

• When other browsers or none are set as default browser:
  

20210423_152756.mp4

@mcarare @ItsDevyani is this the intended behavior?
Will there be a possibility to dismiss it without setting the browser as default?
Should it disappear after setting it as default?

Regarding the issues from above, should I open new bugs?

[mcarare]

@abodea the card goes away only if you set any firefox browser as default. The screen update is made after the preference screen is reloaded. (you navigate away and return). There are no specs regarding the possibility of dismissal with a close button like the card on the home screen.

[ItsDevyani]

agreed, there is no need to have a "dismiss" action in this placement, I'm ok if it disappears and is replaced with Sync once a user has set us as default.