1387984 - Implement notification for out-of-date Firefox users on /firstrun & /whatsnew

Status: RESOLVED FIXED

(www.mozilla.org :: Pages & Content, enhancement)

Description

[Alex Gibson [:agibson]]

In Bug 1381776 we implemented a site wide notification for out-of-date Firefox users that displays a clear CTA for users to update their Firefox. This CTA pointed to /firefox/new?scene=2 and triggers a product (re)download when clicked.

For out-of-date Firefox users on /firstrun & /whatsnew, we'd like to show the same notification, but because those users have only just downloaded the product we'd like to implement  a different behavior:

User clicks CTA -> Modal opens - > Displays text showing them how to update their browser via restart, similar to the instructions in this SUMO article:

https://support.mozilla.org/en-US/kb/update-firefox-latest-version

Comment 1

[Alex Gibson [:agibson]]

Copy: https://docs.google.com/document/d/1UP62TJoBVfz-qPSU8JTCuHsIA5TmPpARxExmf0mFwlI/edit

Comment 2

[Alex Gibson [:agibson]]

Screenshot of update bar on /firstrun

https://screenshots.firefox.com/0j5jIW8Vmx8V6Isy/127.0.0.1

Screenshot of modal window styling after clicking CTA button:

https://screenshots.firefox.com/f8tEjuPSwqAYXFrt/127.0.0.1

Comment 3

[Alex Gibson [:agibson]]

Updated modal styling: https://screenshots.firefox.com/JAsMTbKSpki13mwN/127.0.0.1

Comment 4

[Alex Gibson [:agibson]]

Christa, I've attached a screenshot of the modal in Comment 3 above. This is using our default modal styling, but please let me know if you would like any basic tweaks to the content itself.

Comment 5

[Alex Gibson [:agibson]]

Demo URLs: 

https://bedrock-demo-agibson.us-west.moz.works/en-US/firefox/54.0/firstrun/
https://bedrock-demo-agibson.us-west.moz.works/en-US/firefox/54.0/whatsnew/

Instructions to test
--------------------

1.) Download an older version of Firefox. You can download FF 53.0.2 here: https://ftp.mozilla.org/pub/firefox/releases/53.0.2/.
2.) Once you have installed / opened the browser, open a new tab and type 'about:config'. Accept the warning that is displayed.
3.) On the about:config page, search for 'uitour'.
4.) Verify that 'browser.uitour.enabled' is already set to 'true'.
5.) Next create a new preference (Right click -> New -> String) called 'browser.uitour.testingOrigins'.
6.) Give that preference a value of 'https://bedrock-demo-agibson.us-west.moz.works'
7.) Open a new tab and visit https://bedrock-demo-agibson.us-west.moz.works

If the above steps we're all successful, you should now see the out-of-date notification.

Note: once you click "Update" or close the notification, you will need to clear cookies in order to see it again. You will also only see one variation of the messaging until you clear cookies.

Comment 6

[Alex Gibson [:agibson]]

Peter, do you have any extra GA requirements for this version of the notification? Also, you mentioned wanting to sample rate this version?

Comment 7

[Alex Gibson [:agibson]]

Attachment: GitHub pull request

Comment 8

[pgerman]

Yeah, the requirement here is that we want to be able to throttle the volume of users that see a notification. We may not want to deploy this to to everyone that comes to the page. 

Obviously, we would only want to pass the specialized GA tags for users that see the notification.

Comment 9

[Alex Gibson [:agibson]]

(In reply to pgerman from comment #8)
> Yeah, the requirement here is that we want to be able to throttle the volume
> of users that see a notification. We may not want to deploy this to to
> everyone that comes to the page. 
> 
> Obviously, we would only want to pass the specialized GA tags for users that
> see the notification.

What percentage of users do you want to see the notification?

Comment 10

[Alex Gibson [:agibson]]

(In reply to Alex Gibson [:agibson] from comment #9)
> (In reply to pgerman from comment #8)
> > Yeah, the requirement here is that we want to be able to throttle the volume
> > of users that see a notification. We may not want to deploy this to to
> > everyone that comes to the page. 
> > 
> > Obviously, we would only want to pass the specialized GA tags for users that
> > see the notification.
> 
> What percentage of users do you want to see the notification?

As per convo on Slack:

@pg: Let’s start with something small (5%) then summarize the results and determine if we want millions of people to see this when they boot up firefox for the first time.

Comment 11

[Alex Gibson [:agibson]]

Final criteria for showing the notification:

- Firefox user must be at least 2 major versions out of date from current release version.
- Of those users, initially show the notification for 5% of the audience.

Once we have data on how the notification is performing, we can then look to increasing the threshold or not.

Comment 12

[Alex Gibson [:agibson]]

Demo has now been updated matching the criteria above in Comment 11:

https://bedrock-demo-agibson.us-west.moz.works/en-US/firefox/54.0/firstrun/
https://bedrock-demo-agibson.us-west.moz.works/en-US/firefox/54.0/whatsnew/

Comment 13

[[github robot]]

Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/36f97e38bb4ab853c86d70c8c9e3e6d8e20dd898
[fix bug 1387984] Implement notification for out-of-date Firefox users on /firstrun & /whatsnew

https://github.com/mozilla/bedrock/commit/a7b8adbdea07a23c10cbefcc575641c3403a3286
Merge pull request #5039 from alexgibson/bug-1387984-notification-firstrun-whatsnew

[fix bug 1387984] Implement notification for out-of-date Firefox users on /firstrun & /whatsnew

Comment 14

[[github robot]]

Commits pushed to master at https://github.com/mozmeao/www-config

https://github.com/mozmeao/www-config/commit/8694d9eabe07a17b5fe9646bbeccc8bc7df57426
[fix bug 1387984] Enable out-of-date notice for /firstrun & /whatsnew.

https://github.com/mozmeao/www-config/commit/c84e0e87a22015b3cd1ed94229b75d04b0dc8e37
Merge pull request #32 from jpetto/bug-1387984-notification-whatsnew-firstrun

[fix bug 1387984] Enable out-of-date notice for /firstrun & /whatsnew.