1598498 - Launch new Moments Page about Mobile

Status: RESOLVED FIXED

(Firefox :: Messaging System, task, P2)

Description

[Jim T]

Bugzilla Form: Off-train Moments Page Request

• When (Firefox release or Date) do you expect this to show up to users?:
• What is the Business Goal or Context of the request (brief summary or link)?:
• How will success be measured?:
• Who is the directly accountable/responsible individual making this Messaging Request?
• Please describe the targeting (i.e. which users should see this message) in plain English (e.g. all users who are not signed-in to a Firefox Account in the en-US locale, US region, in Firefox 72 and higher) :
• Enterprise clients included?:
• Link to content or specification of the desired message:
• User impact if declined:
• User risk associated with releasing this Message (High/Med/Low/None):
• Why is the Message risky/not risky? (and alternatives if risky):

Comment 1

[Jim T]

Celeste, please fill out the info above for the next moments page launch. Thanks!

Comment 2

[Jim T]

duplicate comment

Comment 3

[Celeste]

When (Firefox release or Date) do you expect this to show up to users?: 12/13 - 12/20
What is the Business Goal or Context of the request (brief summary or link)?: This is part of the Close the Gap effort. More info can be found in the Moments Page brief.
https://docs.google.com/spreadsheets/d/1GlgDRcL2tMUL-2e-aDsbuLe9MCMi9IcRNgF3BQtCHMQ/edit?usp=sharing
https://docs.google.com/presentation/d/14iVYd1bfMb1SphheGY91lDJ9dBEkfxlIn8g8OzNnVZk/edit?usp=sharing
How will success be measured?: Page view, SMS send, conversion.
Who is the directly accountable/responsible individual making this Messaging Request? Lindsey Shepard
Please describe the targeting (i.e. which users should see this message) in plain English (e.g. all users who are not signed-in to a Firefox Account in the en-US locale, US region, in Firefox 72 and higher) :
--Profile Age (>14 days) (We should discuss timing vs. welcome 2)
--Date Range (11/21 to 11/28)
--Not currently syncing a mobile device
Enterprise clients included?: No
Link to content or specification of the desired message: https://www.mozilla.org/en-US/firefox/welcome/4/
User impact if declined: User will not have Firefox on their mobile device.
User risk associated with releasing this Message (High/Med/Low/None): Low
Why is the Message risky/not risky? (and alternatives if risky): There is no real "trade off" for not completing the CTA. Users who choose not to download Firefox on mobile can continue their current desktop browsing usage.

Comment 4

[Nan Jiang [:nanj]]

Hey Celeste, which locales would this target? For the previous moments pages, we usually targeted the tier-1 locales (en-*, de, fr), if that's the case here, shall we use the URL https://www.mozilla.org/firefox/welcome/4/ instead of https://www.mozilla.org/en-US/firefox/welcome/4/?

Comment 5

[Nan Jiang [:nanj]]

This message has been deployed to stage, we can proceed with QA now.

Notes for QA:

Prerequisites

• Sync CFR messages from Remote Settings stage. You can reference this doc to see how to use the stage environment
• Turn on AS Router devtools by flipping the pref browser.newtabpage.activity-stream.asrouter.devtoolsEnabled
• This message is targeting all channels of Firefox 70 and greater.
• The targeting locale is "en-*", "fr", and "de"
• Another targeting rule is around the browser profile age, it requires the profile age is older than 14 days. You can modify that by updating the created key in {profileDir}/times.json
• It also targets users who have Firefox Account enabled but don't have mobile devices synced.

Steps to test

• Open Firefox 70 or 71
• Open the ASRouter devtools page by clicking the wrench icon on the top right corner of the newtab page
• On the devtools admin page, there is a "Messages" section, open the dropdown list of Show messages form, and select "cfr"
• Scroll down until you find the WNP_MOMENTS_MOBILE message, click on the Show button, then reboot the browser
• Verify that the browser opens the page as https://www.mozilla.org/%LOCALE%/firefox/welcome/4/
• Reboot the browser again, then verify that it opens "about:home" other than the page above

Comment 6

[Celeste]

Yes, Tier 1 languages.

Comment 7

[Eric Renaud [:erenaud]]

Hi Nan - In the case of this page we've been able to expand well past Tier One locales

Here's the list of active locales that should be shown the page, please:

be
cak
cs
cy
de
dsb
en-CA
en-GB
es-AR
es-CL
es-ES
eu
fr
fy-NL
gn
hr
hsb
ia
id
it
ka
kab
nb-NO
nl
nn-NO
pa-IN
pl
pt-BR
ru
sk
sl
sq
sv-SE
tr
vi
zh-CN
zh-TW

Comment 8

[Nan Jiang [:nanj]]

Sure, we can include all those locales for sure.

Cipirian - as the target list gets expanded a lot than the original one specified in the PI, what's your take on this change from QA's perspective?

Comment 9

[Ron Manning]

We will focus on Tier 1 Languages for the Dec 13 deployment. Ciprian, as the other languages are signed off by QA, can we deploy to those as well?

Comment 10

[Nan Jiang [:nanj]]

Hi Cipirian, we'd like to hear your QA sign-off before going further. Could you drop your comment here once you finish all the verification? Per comment 9, we are looking to target Tier 1 locales for the Dec 13 deployment.

Thanks!

Comment 11

[Ciprian Muresan [:cmuresan], Formerly of Ecosystem QA - please needinfo @mcoman for things regarding the team]

We have finished testing the [PI-392] What's New Page for Mobile feature.
QA’s recommendation: GREEN - SHIP IT

Reasoning:

• We haven’t found any issues during testing.

Testing Summary:

• Test Rail

Tested Platforms:

• Windows 10
• Windows 7
• macOS 10.14
• Ubuntu 18.04

Tested Firefox versions:

• Firefox Release 70 en-US
• Firefox Release 71 de
• Firefox Beta 72 fr
• Firefox Nightly 73 en-US

@Ron, judging by the fact that we're not testing the actual content and we only verify triggers, we are seeing two options here:

1. We either select a few of the extra languages to check, which will also cover a bit the visual aspect of the localizations.
   OR
2. Given that the only changes are in the page content and not in code (triggers) we could go forward without the extra check.

Comment 12

[Nan Jiang [:nanj]]

Liz, like bug 1595911, could you take a look at this moments message publishing, please? QA already gave us the go-ahead call, we're looking to enable it on this Friday (Dec 13). This message will be targeting all Tier-1 locales for 70 and beyond.

Thanks!

Comment 13

[Kate Hudson :k88hudson]

@:cmuresan, testing a few of the locales just to ensure redirection is working as expected seems like the right way to go here (it appears the content is ready and translated as far as I can tell)

Comment 14

[Ron Manning]

Hey Pascal, this is ready to be deployed on Friday Dec 13, can we get signoff from RelMan?

Comment 15

[Pascal Chevrel:pascalc]

(In reply to Ron Manning from comment #14)

Hey Pascal, this is ready to be deployed on Friday Dec 13, can we get signoff from RelMan?

Approved for relman.

Comment 16

[Justin Crawford [:hoosteeno] [:jcrawford]]

A PR is going into bedrock now to enable SMS in de/fr: https://github.com/mozilla/bedrock/pull/8314

Comment 17

[Justin Crawford [:hoosteeno] [:jcrawford]]

The SMS functionality is not working in Germany. We will ship all locales except Germany (de) on Friday 2019-12-13. Here is the list from comment 7 with de excised:

be
cak
cs
cy
dsb
en-CA
en-GB
es-AR
es-CL
es-ES
eu
fr
fy-NL
gn
hr
hsb
ia
id
it
ka
kab
nb-NO
nl
nn-NO
pa-IN
pl
pt-BR
ru
sk
sl
sq
sv-SE
tr
vi
zh-CN
zh-TW

We will update the bug with a ship date for Germany.

Comment 18

[Nan Jiang [:nanj]]

We have deployed this message to production.

Note that it's currently targeting all Tier-1 locales except de, will add it back in once it's ready.

Comment 19

[Justin Crawford [:hoosteeno] [:jcrawford]]

The SMS messages sent at the 11th hour in Germany were slow to arrive, but they did arrive. We can ship Germany.

Comment 20

[Nan Jiang [:nanj]]

Okay, deploying it with de.

Comment 21

[Nan Jiang [:nanj]]

Update: de has been added to the targeting.

All Tier-1 locales are live now, marking this bug as fixed.

Comment 22

[Nan Jiang [:nanj]]

Update: we have disabled this moments page as planned.