Closed Bug 1698962 Opened 1 month ago Closed 1 month ago

Land "Pin Firefox" onboarding strings in nightly ahead of changing default in beta

Categories

(Firefox :: Messaging System, enhancement, P1)

enhancement

Tracking

()

VERIFIED FIXED
88 Branch
Iteration:
88.2 - Mar 8 - Mar 21
Tracking Status
firefox88 --- verified

People

(Reporter: Mardak, Assigned: Mardak)

References

(Blocks 1 open bug)

Details

Attachments

(3 files)

Bug 1694257 should allow us to change the default onboarding experience with "just" JSON to uplift. The default chosen will be based on the experiment using bug 1686343 with 4 treatment branches that will run in 87 release, so we would only know initial results during 88 beta.

flod, does it make sense to land strings in 88 nightly for potential default change during 88 beta? One of the potential winning branch looks like attachment 9204059 [details] (with an additional "Choose Firefox under Web browser when your settings open" when clicking on the button, so 5 new strings), but there's other experiment branches with different strings maybe ~5 additional new strings.

Should we land all ~10 strings in 88 nightly and clean up in 89 nightly when picking a default? Or maybe land with ~5 strings for the branch we think might win?

Flags: needinfo?(francesco.lodolo)

I guess it depends on how certain you are about the winning option.

I would point out that this is already quite late for 88, since Friday is string freeze for mozilla-central. Do we have mechanism to avoid enabling the experiment if those strings are not localized?

Flags: needinfo?(francesco.lodolo)

The experiment will run with hardcoded english strings targeting en-* users, so we don't need to land strings for the experiment. This bug is in preparation for changing the default experience similar to changing it to show "set default" on the first page from bug 1691145, which I believe wanted to be turned on in 86 during beta but strings were not landed during nightly 86.

adavis, do we have a sense on which "pin" branch will win, so we can land those strings and avoid localizing the other branches' strings? And if it does indeed win, we can probably turn it on by default during beta 88 instead of doing the 100% en-* rollout behavior for "set default?"

Flags: needinfo?(adavis)

do we have a sense on which "pin" branch will win, so we can land those strings and avoid localizing the other branches' strings?

So, my money is on treatment D but we test things because we're never 100% sure. So if we start localization (which makes sense), note that it's a bit of a gamble (though probably better than localizing all 4 treatments).

we can probably turn it on by default during beta 88 instead of doing the 100% en-* rollout behavior for "set default?"

Trying to roll out the winner in 88 would be awesome and save us an entire train. I'd argue that we'll probably still want to do a 100% en-* rollout for 2 weeks until 88 lands. Landing it in 88 means that we only need to use Nimbus for 2 weeks to roll it out while we wait.

Flags: needinfo?(adavis)
Blocks: 1699237

Adding treatment D screenshots in the bug for easy access

Pushed by elee@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/e584ce3182e1
Land "Pin Firefox" onboarding strings in nightly ahead of changing default in beta r=pdahiya,fluent-reviewers,flod
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 88 Branch
Iteration: --- → 88.2 - Mar 8 - Mar 21
Priority: -- → P1

Marking this enhancemend as VERIFIED based on the work done on PI-983.

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.