[Experiment] Hold back study comparing new proton about:welcome design with previous onboarding
Categories
(Firefox :: Messaging System, task, P2)
Tracking
()
People
(Reporter: pdahiya, Assigned: pdahiya)
References
(Blocks 1 open bug)
Details
(Whiteboard: [proton-onboarding] [priority:2a])
See https://mana.mozilla.org/wiki/display/FIREFOX/New+Identity+Based+User+Onboarding+Experiment
This is offtrain targeting Fx89
Assignee | ||
Comment 1•3 years ago
|
||
Ana to help create the recipe and file PI bug for this
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 2•3 years ago
|
||
Here are (both draft):
- PI ticket: https://jira.mozilla.com/browse/PI-1048
- Nimbus experiment recipe: https://experimenter.services.mozilla.com/nimbus/multistage-aboutwelcome-mr1-design/edit/overview
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 3•3 years ago
|
||
Marking it P2 in favor of proton onboarding priority flags
Comment 4•3 years ago
•
|
||
Because of bug 1711700, we cannot enable the branch with just an empty object (attempting to use the normal non-experiment screens) and will need to specify screens
in the JSON. We can workaround by providing a screens
array which will dynamically switch a "default" button to "primary" button for users who can and need to pin:
However, the string that gets used has slightly different casing than what is currently shown in 88:
mr1-onboarding-set-default-pin-primary-button-label =
Make { -brand-short-name } my primary browser
.title = Sets { -brand-short-name } as default browser and pins to taskbar
onboarding-multistage-pin-default-primary-button-label = Make { -brand-short-name } My Primary Browser
There are also other changes that happen when Firefox can be pinned for the holdback group, e.g., different text, default gif when waiting for default:
https://searchfox.org/mozilla-central/rev/443f87caa5fadba920b0382e12874693d6c6133a/browser/components/newtab/aboutwelcome/lib/AboutWelcomeDefaults.jsm#445-489
So we can switch the targeting to be windows 10 1903+ and assume firefox will need to be pinned. Or keep the current targeting of first startup en users and always show "default" even if firefox needs to be pinned?
Updated•3 years ago
|
Comment 5•3 years ago
|
||
With bug 1711700 wontfix for 89, we'll need to either:
- target recent win 10 and show the "primary browser" welcome
- show "default browser" targeting general firststartup (windows)
Assignee | ||
Updated•3 years ago
|
Updated•3 years ago
|
Description
•