1136008 - Mozilla.org FF38.1 /whatsnew - Copy

Status: RESOLVED FIXED

(Marketing :: Copy, task)

Description

[Cory Price [:ckprice] (bugmail disabled, NI me!)]

This bug is created to execute the copy writing for /whatsnew and /firstrun tours launching in FF38 (May 12th).

Product string freeze is March 15th.
Web string freeze is April 6th.

Wiki: https://wiki.mozilla.org/Firefox_Growth_Campaign_2015
Schedule: https://app.smartsheet.com/b/publish?EQBCT=e4dd7a95c9e54bec8fb6e6c0af359460

Comment 1

[Cory Price [:ckprice] (bugmail disabled, NI me!)]

Attachment: /firstrun Copy Document

Comment 2

[Cory Price [:ckprice] (bugmail disabled, NI me!)]

/firstrun Copy Document - https://docs.google.com/a/mozilla.com/document/d/1kIxhsFy_8wGDg00xBqIj4WmXtX7s3MaQmAqoxdYIL8Y/edit#heading=h.b0vut9xst3js

(Added as an attachment, but Bugzilla didn't convert to link)

Comment 3

[Cory Price [:ckprice] (bugmail disabled, NI me!)]

Wireframes are in 

Ideal flow bug1129548comment3
Fallback flow bug1129548comment4

Comment 4

[Cory Price [:ckprice] (bugmail disabled, NI me!)]

/whatsnew UX final - https://bugzilla.mozilla.org/show_bug.cgi?id=1129545#c3
/firstrun UX final - https://bugzilla.mozilla.org/show_bug.cgi?id=1129548#c5

Comment 5

[Matej Novak [:matej]]

(In reply to Cory Price [:ckprice] from comment #4)
> /whatsnew UX final - https://bugzilla.mozilla.org/show_bug.cgi?id=1129545#c3
> /firstrun UX final - https://bugzilla.mozilla.org/show_bug.cgi?id=1129548#c5

Not totally sure what the flag is for, but thanks for the links.

Comment 6

[Cory Price [:ckprice] (bugmail disabled, NI me!)]

Updating to reflect that this bug will only track /whatsnew copy for 38.1.

/firstrun copy is tracked in the bug 1149684 tracker.

Comment 7

[Cory Price [:ckprice] (bugmail disabled, NI me!)]

Hey Matej, how is Tuesday for copy here? I also requested in the design bug 1136929 for design by Tuesday.

Thanks

Comment 8

[Matej Novak [:matej]]

(In reply to Cory Price [:ckprice] from comment #7)
> Hey Matej, how is Tuesday for copy here? I also requested in the design bug
> 1136929 for design by Tuesday.
> 
> Thanks

Plausible!

Troy, WDYT?

Comment 9

[Troy Palmer]

Plausible indeed.

(In reply to Matej Novak [:matej] from comment #8)
> (In reply to Cory Price [:ckprice] from comment #7)
> > Hey Matej, how is Tuesday for copy here? I also requested in the design bug
> > 1136929 for design by Tuesday.
> > 
> > Thanks
> 
> Plausible!
> 
> Troy, WDYT?

Comment 10

[Troy Palmer]

Hi everyone

Here is the link to g-doc for the What's New page (and variations)

https://docs.google.com/document/d/1gYyaZfFpUp5duSMG7gqRq0EyQamUw-hY_6qxgWrM2ow/edit?usp=sharing

Let me know if there are any questions.

Thanks,
Troy

Comment 11

[Alex Gibson [:agibson]]

Troy,

For locales that don't get the widget and should see download links/buttons for the app stores instead, what strings should we be using for the buttons?

Comment 12

[Matej Novak [:matej]]

(In reply to Alex Gibson [:agibson] from comment #11)
> Troy,
> 
> For locales that don't get the widget and should see download links/buttons
> for the app stores instead, what strings should we be using for the buttons?

Aren't we using the App Store and Google Play buttons for those?

Comment 13

[Alex Gibson [:agibson]]

(In reply to Matej Novak [:matej] from comment #12)
> (In reply to Alex Gibson [:agibson] from comment #11)
> > Troy,
> > 
> > For locales that don't get the widget and should see download links/buttons
> > for the app stores instead, what strings should we be using for the buttons?
> 
> Aren't we using the App Store and Google Play buttons for those?

This is something I'm not entirely clear on, but even so those should have alt text. Can someone link to the buttons we should be using for reference?

Comment 14

[Cory Price [:ckprice] (bugmail disabled, NI me!)]

We decided that if they are on desktop they should see our buttons. If they are on mobile, they should see badges.

Looking for copy now.

Comment 15

[Alex Gibson [:agibson]]

(In reply to Cory Price [:ckprice] from comment #14)
> We decided that if they are on desktop they should see our buttons. If they
> are on mobile, they should see badges.
> 
> Looking for copy now.

I'm going ahead and adding the following strings for the CTA buttons when users don't get the widget:

"Get Firefox for Android"
"Get Firefox for iOS"

Note users will never be on mobile and see badges on this page, since /whatsnew is Firefox only.

If these strings are incorrect, someone please let me know today.

Comment 16

[Matej Novak [:matej]]

(In reply to Alex Gibson [:agibson] from comment #15)
> (In reply to Cory Price [:ckprice] from comment #14)
> > We decided that if they are on desktop they should see our buttons. If they
> > are on mobile, they should see badges.
> > 
> > Looking for copy now.
> 
> I'm going ahead and adding the following strings for the CTA buttons when
> users don't get the widget:
> 
> "Get Firefox for Android"
> "Get Firefox for iOS"
> 
> Note users will never be on mobile and see badges on this page, since
> /whatsnew is Firefox only.
> 
> If these strings are incorrect, someone please let me know today.

The current button on /android says "Download on Google Play." We also have some versions that say "Get it free on Google Play."

If we're OK straying from that, the above lines looks good to me.

Comment 17

[Alex Gibson [:agibson]]

(In reply to Matej Novak [:matej] from comment #16)
> The current button on /android says "Download on Google Play." We also have
> some versions that say "Get it free on Google Play."
> 
> If we're OK straying from that, the above lines looks good to me.

I thought of this also, but in this context we're displaying two separate buttons for two different platforms.

"Get it free on Google Play." and "Download on Google Play." don't make it clear which product it's talking about specifically. I guess most users will work it out, but I think calling out each platform specifically in the text seemed a bit clearer. Thoughts?

Comment 18

[Matej Novak [:matej]]

(In reply to Alex Gibson [:agibson] from comment #17)
> (In reply to Matej Novak [:matej] from comment #16)
> > The current button on /android says "Download on Google Play." We also have
> > some versions that say "Get it free on Google Play."
> > 
> > If we're OK straying from that, the above lines looks good to me.
> 
> I thought of this also, but in this context we're displaying two separate
> buttons for two different platforms.
> 
> "Get it free on Google Play." and "Download on Google Play." don't make it
> clear which product it's talking about specifically. I guess most users will
> work it out, but I think calling out each platform specifically in the text
> seemed a bit clearer. Thoughts?

That makes sense, though I'm still in favor of using the badges across the board.

Comment 19

[Cory Price [:ckprice] (bugmail disabled, NI me!)]

Considering the iOS/Pocket pivot, closing these bugs and opening new ones.