Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

Fenix New Tab Experiment (Test branch 3: Default Browser Message to a new user on their third session, Control: No Message) #18375

Closed
ItsDevyani opened this issue Mar 8, 2021 · 9 comments
Assignees
Labels
E3 Estimation Point: average, 2 - 3 days eng:qa:verified QA Verified Feature:Experiments A category for experiment-related features. Feature:Notifications Feature:Telemetry Nimbus
Milestone

Comments

@ItsDevyani
Copy link

ItsDevyani commented Mar 8, 2021

User Story

  • As a user, I want to know how I can easily set up Fenix as my default browser once I've had a chance to use the browser a few times.

Dependencies

  • Test Measurement plan is being requested by the DS team
  • Default Browser Dashboard is also being requested by the DS team
  • Nimbus SDK integration with Fenix
    - UX design work is done
  • Engineering Time

Acceptance Criteria

  • A Message/Notification can be triggered to a user on their third session with Fenix.
  • A user can click the notification and be launched into the Default Browser flow.
  • Funnel Activity (Clicks on each step) and Conversion to the default browser feature can be measured.
  • Nimbus SDK integration with New Tab allowing experimentation on it

Engineering notes

  • Nimbus engineering docs
  • Please sync with data science before starting this implementation to confirm the following:

Experiment length: TBD (default: 35 days total, 7 day enrollment period)
Start date: TBD
Experiment size: TBD
A/B split: TBD (default: 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.

┆Issue is synchronized with this Jira Task

@github-actions github-actions bot added the needs:triage Issue needs triage label Mar 8, 2021
@ItsDevyani
Copy link
Author

Project Update:

  • Nicole Weber has made the designs for this experiment and they are ready to be shared as needed.
  • We have has discussions with the Nimbus Team to launch this as a Nimbus Experiment.

@ItsDevyani ItsDevyani changed the title Fenix Default Browser In product Notification to a user on their third session. Fenix New Tab Experiment: Default Browser Message to a user on their third session Mar 23, 2021
@ItsDevyani ItsDevyani changed the title Fenix New Tab Experiment: Default Browser Message to a user on their third session Fenix New Tab Experiment (Test: Default Browser Message to a new user on their third session, Control: No Message) Mar 23, 2021
@eliserichards eliserichards added Feature:Experiments A category for experiment-related features. E3 Estimation Point: average, 2 - 3 days labels Mar 26, 2021
@amedyne amedyne changed the title Fenix New Tab Experiment (Test: Default Browser Message to a new user on their third session, Control: No Message) Fenix New Tab Experiment (Test branch 3: Default Browser Message to a new user on their third session, Control: No Message) Apr 5, 2021
@amedyne
Copy link
Contributor

amedyne commented Apr 5, 2021

Note: This ticket will be for tracking the Engineering tasks for developing Experiment Test Branch 3: Default Browser Message to a new user on their third session and the corresponding telemetry needed for this branch.

@amedyne amedyne removed the Leanplum label Apr 5, 2021
@mcarare mcarare self-assigned this Apr 7, 2021
@mcarare mcarare added the Nimbus label Apr 7, 2021
@mcarare
Copy link
Contributor

mcarare commented Apr 7, 2021

Question for @ItsDevyani or UX related to timing:
The other experiment branches do not have a timing related condition like this one:

on their third session with Fenix.

Is this influencing the experiment?

Another question: if we keep the timing, should the message be shown on the home screen only on the third session, or in each one from that point forward? In the Figma designs, we have a close button. Is clicking this supposed to dismiss the message and also prevent it from showing again? (again, this differs from the "fixed" options in the other branches).

I am ok with either decision, I would just like to note that if we would show the message only on the third session there might be cases where a user never sees the message, as opening the browser on the last visited tab will skip showing the home screen.

@amedyne
Copy link
Contributor

amedyne commented Apr 7, 2021

Tagging @topotropic , too.

@ItsDevyani
Copy link
Author

Is this influencing the experiment?

We are comparing three tactics against each other, this is one of those 3 tactics, so showing a banner on the new tab to a new user on their 3rd app open after installing the app is a factor that influences the experiment.

Another question: if we keep the timing, should the message be shown on the home screen only on the third session, or in each one from that point forward? In the Figma designs, we have a close button. Is clicking this supposed to dismiss the message and also prevent it from showing again? (again, this differs from the "fixed" options in the other branches).

Once the message shows, it should keep showing till the user either clicks the 'x' button to dismiss or clicks the 'set to default' button. once the message clears it gone forever.

I am ok with either decision, I would just like to note that if we would show the message only on the third session there might be cases where a user never sees the message, as opening the browser on the last visited tab will skip showing the home screen.

noted that makes sense.

@mcarare
Copy link
Contributor

mcarare commented Apr 8, 2021

Another question: Is this supposed to be shown in private browsing too?

mcarare added a commit to mcarare/fenix that referenced this issue Apr 8, 2021
mcarare added a commit to mcarare/fenix that referenced this issue Apr 8, 2021
mcarare added a commit to mcarare/fenix that referenced this issue Apr 8, 2021
@amedyne
Copy link
Contributor

amedyne commented Apr 8, 2021

Another question: Is this supposed to be shown in private browsing too?

Per @ItsDevyani , no notification in private browsing.

mcarare added a commit to mcarare/fenix that referenced this issue Apr 9, 2021
mcarare added a commit to mcarare/fenix that referenced this issue Apr 9, 2021
mcarare added a commit to mcarare/fenix that referenced this issue Apr 9, 2021
mcarare added a commit to mcarare/fenix that referenced this issue Apr 9, 2021
mcarare added a commit to mcarare/fenix that referenced this issue Apr 9, 2021
mcarare added a commit to mcarare/fenix that referenced this issue Apr 9, 2021
mcarare added a commit to mcarare/fenix that referenced this issue Apr 9, 2021
mcarare added a commit to mcarare/fenix that referenced this issue Apr 12, 2021
mcarare added a commit to mcarare/fenix that referenced this issue Apr 13, 2021
mcarare added a commit to mcarare/fenix that referenced this issue Apr 13, 2021
@lobontiumira
Copy link

Hi all,

I was able to trigger the "Set as default browser" card on the homescreen, after the following steps:

  • open the app, browse a page at least, close the app, not just background it,
  • open the app for the second time, do the same actions as in the previous step,
  • open the third session, browse a few pages, close again the app, not just background it,
  • the fourth time, when opened, go to the homescreen, and the "Set as default browser" card is displayed.

Tapping on the "Set as default browser" button, redirect the user to set the default browser.
Tapping on the "x" from the card, dismisses the card, and does not show it again.

Tested on Google Pixel (Android 10), and OnePlus 5T (Android 10), on a debug Nightly build #2015805929, GV 89.0a1-20210418092832.

Note: even if clearing the data from the device's settings-apps, the card on the homescreen is no longer displayed. Uninstalling and reinstalling the app, redisplayes the card.

new.tab.experiment.mp4

@ItsDevyani should I test anything else regarding this issue?
Thank you!

@lobontiumira lobontiumira added the eng:qa:verified QA Verified label Apr 23, 2021
@ItsDevyani
Copy link
Author

@lobontiumira I think that is fine. Thanks for confirming.

@sflorean sflorean closed this as completed May 6, 2021
@gabrielluong gabrielluong added this to the 89 milestone May 31, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
E3 Estimation Point: average, 2 - 3 days eng:qa:verified QA Verified Feature:Experiments A category for experiment-related features. Feature:Notifications Feature:Telemetry Nimbus
Projects
None yet
Development

No branches or pull requests

8 participants