We recently ran an experiment to test out using an infobar to ask users to set Firefox as default. We felt it was a less invasive way to ask than the existing modal prompt. Unfortunately, it did not perform anywhere near as well as our existing modal prompt displayed as of first startup and until permanently dismissed but we agreed that the infobar can still play an important role at reaching out to our existing users in a respectful way. Spec: - Display a similar infobar as the one from our past experiment (https://jira.mozilla.com/browse/UJET-66) - Display the infobar every 5 weeks to existing users if they have not set Firefox as default yet. - Do a 1-click on Win 10 at the same time as setting to default Strings Body[1]: Make Firefox your primary browser? Put Protection, privacy and speed on autopilot. Button[2]: Make Firefox my primary browser This is a minimal change to the body. The button is to align with other touchpoints that will be using this language. [1] There's only one change vs our experiment copy. Replace default with primary. [2] Instead of set as default. Why 5 weeks? - It's often enough that it may have impact on browser usage. - It's not often enough that it will annoy users. NOTE: Getting something out quickly is really important. If it is easier and more importantly faster, this work can be split into parts: - Deploying the existing infobar with set to default functionality and existing strings at a frequency of 5 week intervals - And then, adding the pin functionality and changing the strings.
Bug 1703874 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
We recently ran an experiment to test out using an infobar to ask users to set Firefox as default. We felt it was a less invasive way to ask than the existing modal prompt. Unfortunately, it did not perform anywhere near as well as our existing modal prompt displayed as of first startup and until permanently dismissed but we agreed that the infobar can still play an important role at reaching out to our existing users in a respectful way. Spec: - Display a similar infobar as the one from our past experiment (https://jira.mozilla.com/browse/UJET-66) - Display the infobar every 5 weeks to existing users if they have not set Firefox as default yet. - Do a 1-click on Win 10 at the same time as setting to default - Only display to users who dismissed the modal prompt - Avoid collision with existing user onboarding Strings Body[1]: Make Firefox your primary browser? Put Protection, privacy and speed on autopilot. Button[2]: Make Firefox my primary browser This is a minimal change to the body. The button is to align with other touchpoints that will be using this language. [1] There's only one change vs our experiment copy. Replace default with primary. [2] Instead of set as default. Why 5 weeks? - It's often enough that it may have impact on browser usage. - It's not often enough that it will annoy users. NOTE: Getting something out quickly is really important. If it is easier and more importantly faster, this work can be split into parts: - Deploying the existing infobar with set to default functionality and existing strings at a frequency of 5 week intervals - And then, adding the pin functionality and changing the strings.
We recently ran an experiment to test out using an infobar to ask users to set Firefox as default. We felt it was a less invasive way to ask than the existing modal prompt. Unfortunately, it did not perform anywhere near as well as our existing modal prompt displayed as of first startup and until permanently dismissed but we agreed that the infobar can still play an important role at reaching out to our existing users in a respectful way. Spec: - Display a similar infobar as the one from our past experiment (https://jira.mozilla.com/browse/UJET-66) - Display the infobar every 5 weeks to existing users if they have not set Firefox as default yet. - Do a 1-click on Win 10 at the same time as setting to default - Only display to users who dismissed the modal prompt - Avoid collision with existing user onboarding (MR1) Strings Body[1]: Make Firefox your primary browser? Put Protection, privacy and speed on autopilot. Button[2]: Make Firefox my primary browser This is a minimal change to the body. The button is to align with other touchpoints that will be using this language. [1] There's only one change vs our experiment copy. Replace default with primary. [2] Instead of set as default. Why 5 weeks? - It's often enough that it may have impact on browser usage. - It's not often enough that it will annoy users. NOTE: Getting something out quickly is really important. If it is easier and more importantly faster, this work can be split into parts: - Deploying the existing infobar with set to default functionality and existing strings at a frequency of 5 week intervals - And then, adding the pin functionality and changing the strings.
We recently ran an experiment to test out using an infobar to ask users to set Firefox as default. We felt it was a less invasive way to ask than the existing modal prompt. Unfortunately, it did not perform anywhere near as well as our existing modal prompt displayed as of first startup and until permanently dismissed but we agreed that the infobar can still play an important role at reaching out to our existing users in a respectful way. Spec: - Display a similar infobar as the one from our past experiment (https://jira.mozilla.com/browse/UJET-66) - Display the infobar every 5 weeks to existing users if they have not set Firefox as default yet. - Do a 1-click on Win 10 at the same time as setting to default - Only display to users who dismissed the modal prompt - Avoid collision with existing user onboarding (MR1) - Display on content pages (though initially it may be easier on New Tab) Strings Body[1]: Make Firefox your primary browser? Put Protection, privacy and speed on autopilot. Button[2]: Make Firefox my primary browser This is a minimal change to the body. The button is to align with other touchpoints that will be using this language. [1] There's only one change vs our experiment copy. Replace default with primary. [2] Instead of set as default. Why 5 weeks? - It's often enough that it may have impact on browser usage. - It's not often enough that it will annoy users. NOTE: Getting something out quickly is really important. If it is easier and more importantly faster, this work can be split into parts: - Deploying the existing infobar with set to default functionality and existing strings at a frequency of 5 week intervals - And then, adding the pin functionality and changing the strings.
We recently ran an experiment to test out using an infobar to ask users to set Firefox as default. We felt it was a less invasive way to ask than the existing modal prompt. Unfortunately, it did not perform anywhere near as well as our existing modal prompt displayed as of first startup and until permanently dismissed but we agreed that the infobar can still play an important role at reaching out to our existing users in a respectful way. Spec: - Display a similar infobar as the one from our past experiment (https://jira.mozilla.com/browse/UJET-66) - Display the infobar every 5 weeks to existing users if they have not set Firefox as default yet. - Do a 1-click on Win 10 at the same time as setting to default - Only display to users who dismissed the modal prompt - Avoid collision with existing user onboarding (MR1) - Display on content pages (though initially it may be easier on New Tab to start) Strings Body[1]: Make Firefox your primary browser? Put Protection, privacy and speed on autopilot. Button[2]: Make Firefox my primary browser This is a minimal change to the body. The button is to align with other touchpoints that will be using this language. [1] There's only one change vs our experiment copy. Replace default with primary. [2] Instead of set as default. Why 5 weeks? - It's often enough that it may have impact on browser usage. - It's not often enough that it will annoy users. Following discussions with Andrei: Getting something out quickly is really important. If it is easier and more importantly faster, this work can be split into parts: 1- Deploying the existing infobar with set to default and pin functionality and existing strings at a frequency of 5 week intervals 2- And then, change the strings and display on content pages. (not just new tab)