Additional "default browser" prompts: variant 2 #5476
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Task/Issue URL: https://app.asana.com/0/1208671518894266/1208944504536347/f
Description
Introduces variant 2 of the experiment that proposes new CTAs around setting DDG as a default browser. The PR also adds all of the experiment foundations and abstractions, so the remaining two variants will only be a small formality.
I'm going to follow up on pixels in a separate PR.
Class diagram
Flow diagram
Steps to test this PR
This PR relies on the new A/B/N framework for rollout, so to test you'll need a custom privacy config which includes the feature definition, for example:
or you can apply this JSON Blob:
Once built with the right config, ensure that you don't have DDG app set as a default browser, only then you'll be assigned to the experiment.
Given the example config above:
If you convert at any point and set DDG app as default browser, the experiment will permanently stop.
Screen_recording_20250115_173728.webm
In the video I'm using the ADB commands to change the date, but any mechanism of date change will be enough :)