1149685 - Create static snippet on fxa confirmation page promoting fx mobile

Status: RESOLVED FIXED

(Firefox :: Sync, defect)

Description

[Chris More [:cmore]]

Github issue: https://github.com/mozilla/fxa-content-server/issues/2255

Comment 1

[Jonathan Petto [:jpetto]]

Requirements doc: https://docs.google.com/a/mozilla.com/document/d/1h_JPSnbWqqyyf45F-3hMtmG6xjWNG3ky33UU7UDw8nk/edit#heading=h.f2le2z593kr5

Copy doc (in-progress): https://docs.google.com/a/mozilla.com/document/d/1hnsylYMQx12yXqGQaR_gfZlNKyo6F6adhA_ramsnN1c/edit

Code samples:
  template: https://github.com/mozilla/fxa-content-server/blob/master/app/scripts/templates/marketing_snippet.mustache
  view: https://github.com/mozilla/fxa-content-server/blob/master/app/scripts/views/marketing_snippet.js
  style: https://github.com/mozilla/fxa-content-server/blob/master/app/styles/modules/_marketing.scss

Comment 2

[Chris More [:cmore]]

note to self: generate URLs for app stores with campaign parameters.

Comment 3

[Jennifer Bertsch [:jbertsch]]

Hi Cmore and Jon-

A couple of questions on this one:

1.  Is this a spring campaign bug that Cory should be tracking?

2.  Also is this literally a snippet?  If yes, should the dev work then be tracked in the Snippet product and not here?

Thx,
Jen

Comment 4

[Chris More [:cmore]]

(In reply to Jennifer Bertsch [:jbertsch] from comment #3)
> Hi Cmore and Jon-
> 
> A couple of questions on this one:
> 
> 1.  Is this a spring campaign bug that Cory should be tracking?
> 
> 2.  Also is this literally a snippet?  If yes, should the dev work then be
> tracked in the Snippet product and not here?
> 
> Thx,
> Jen

1) This is part of the flow for the 38.1 first run and doesn't have a campaign component for the snippet itself.

2) This is not an about:home snippet. This is a snippet (same name) on the Firfox sync confirmation page. 

I adjusted the product/component to be the Mozilla Services.

Comment 5

[Chris More [:cmore]]

Jon: For 38.0.5, we need to remove the button for iOS as it is not ready.

We have two options here:

1) Remove the iOS button and iOS variation of the snippet complete.

2) Keep the variations, and replace the button with a string that is already localized:

Firefox is coming soon to iOS! <a href="{url}">Sign up to learn more</a>

where the URL is https://www.mozilla.org/newsletter/ios/

I like option 2:.

Let's get feedback.

Comment 6

[Holly Habstritt Gaal [:Habber]]

(In reply to Chris More [:cmore] from comment #5)
> Jon: For 38.0.5, we need to remove the button for iOS as it is not ready.
> 
> We have two options here:
> 
> 1) Remove the iOS button and iOS variation of the snippet complete.
> 
> 2) Keep the variations, and replace the button with a string that is already
> localized:
> 
> Firefox is coming soon to iOS! <a href="{url}">Sign up to learn more</a>
> 
> where the URL is https://www.mozilla.org/newsletter/ios/
> 
> I like option 2:.
> 
> Let's get feedback.

+1 on the option to sign up to learn more so that iOS users have an option here. Jon can take a pass at implementing this in code and then we can give design feedback. 

I'd recommend displaying the Android button first and the iOS messaging + "sign up to learn more" link below.

Comment 7

[Chris More [:cmore]]

Shane/Ryan: What is possible here given the fxa push schedule? A few options:

1) Don't launch the new snippet and keep the old snippet that has the android guy and play store link. (what we have now and don't enable the flag)

2) Change the snippet that jpetto submitted to the fxa team, which will introduce new new strings. We have those strings translated in bedrock, but it would have to be moved over to the fxa system.

3) Remove the iOS variation button / copy and just stick with the android variation of jpetto's snippet. (basically the same as option 1 and probably not really worth it)

Please let us know what is possible in this time. The dev work is straightforward and mainly impacts L10N and fxa push train.

Comment 8

[Shane Tomlinson [:stomlinson]]

:cmore, I am lacking some context

Comment 9

[Shane Tomlinson [:stomlinson]]

> :cmore, I am lacking some context

Woops, that was a partial thought that I meant to complete before adding rfk. After reading through this, I have the context.

I have to see where we are in the train and whether the strings for FxA train 37 have been cut. If not, we may be able to sneak this change in before they are.

Comment 10

[Shane Tomlinson [:stomlinson]]

:cmore - if the change goes ahead, do we still need to hold off until June 2nd to release the snippet? If not, we can release the snippet with FxA train 37, which should go out the week of May 18th.

Comment 11

[Jonathan Petto [:jpetto]]

:stomlinson - I'm pretty sure we'll still want to wait for the spring campaign start date of 6/2 to launch the snippet. :cmore - can you verify?

I'm working on a branch/PR for scenario #2 - introducing new strings for the iOS sections. I'm currently using "Firefox is coming soon to iOS!" and "Sign up to learn more". Is this the direction we want? We could also re-use the existing string "Download Firefox for iOS.", but I would say that's not optimal.

:habber/:cmore - thoughts on the strings?

Comment 12

[Jonathan Petto [:jpetto]]

Attachment: proposed-desktop.png

Proposed new strings for desktop users.

Comment 13

[Jonathan Petto [:jpetto]]

Attachment: proposed-ios.png

Proposed new strings for iOS users.

Comment 14

[Holly Habstritt Gaal [:Habber]]

(In reply to Jon Petto [:jpetto] from comment #11)
> :stomlinson - I'm pretty sure we'll still want to wait for the spring
> campaign start date of 6/2 to launch the snippet. :cmore - can you verify?
> 
> I'm working on a branch/PR for scenario #2 - introducing new strings for the
> iOS sections. I'm currently using "Firefox is coming soon to iOS!" and "Sign
> up to learn more". Is this the direction we want? We could also re-use the
> existing string "Download Firefox for iOS.", but I would say that's not
> optimal.
> 
> :habber/:cmore - thoughts on the strings?

Those strings work for me. They are already existing and they are what we are currently using on /new for iOS users to tell them that iOS is coming soon. "Download Firefox for iOS" would be misleading.

Comment 15

[Chris More [:cmore]]

(In reply to Jon Petto [:jpetto] from comment #11)
> :stomlinson - I'm pretty sure we'll still want to wait for the spring
> campaign start date of 6/2 to launch the snippet. :cmore - can you verify?

Yes, this snippet won't launch until June 2nd.

:stomlinson: given that we are changing strings now and this snippet needs to go out on June 2nd (fx 38.0.5), are we alright on that train in regards to timing?

> 
> I'm working on a branch/PR for scenario #2 - introducing new strings for the
> iOS sections. I'm currently using "Firefox is coming soon to iOS!" and "Sign
> up to learn more". Is this the direction we want? We could also re-use the
> existing string "Download Firefox for iOS.", but I would say that's not
> optimal.
> 
> :habber/:cmore - thoughts on the strings?

:jpetto: +1 on the strings for desktop and iOS in comment 12 and comment 13.

Link should point to: hhttps://www.mozilla.org/newsletter/ios/

Comment 16

[Shane Tomlinson [:stomlinson]]

> :stomlinson: given that we are changing strings now and this snippet needs to go out on June 2nd (fx 38.0.5), are we alright on that train in regards to timing?

We are on it [1]! Both new strings are already merged into the content server and should be extracted for the localizers today or tomorrow.

[1] - https://github.com/mozilla/fxa-content-server/blob/master/app/scripts/lib/strings.js#L21-L24

Comment 17

[Shane Tomlinson [:stomlinson]]

This work was merged into the content server in two patches:

[1] - https://github.com/mozilla/fxa-content-server/pull/2350
[2] - https://github.com/mozilla/fxa-content-server/pull/2382

Closing as fixed.