1139716 - Update Android product page to add Reading List - Development

Status: RESOLVED FIXED

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

Description

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

New request from PMM to update the Android page to

- Update page to highlight Reading List
- Revise the page to show tablet devices next to the mobile phone at the top of the page.

Comment 1

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

This is ready for development.

Design with copy (includes notes for mobile): https://bugzilla.mozilla.org/show_bug.cgi?id=1139715#c12

Note that the two CTA's (GET FIREFOX FOR ANDROID) will both trigger the Send to device widget modal (bug 1146528), which is not yet developed.

Comment 2

[Alex Gibson [:agibson]]

Attachment: GitHub pull request

Still waiting on some final assets from creative, but I've opened a PR and marked as WIP.

Please note this PR does not include the SMS widget, which has yet to be developed. The Reading List section of the features accordion is behind a waffle flag which we can flip on once 38.1 is out.

Comment 3

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

:agibson - Android strings final! bug 1139715 comment 34

Comment 4

[Alex Gibson [:agibson]]

(In reply to Cory Price [:ckprice] from comment #3)
> :agibson - Android strings final! bug 1139715 comment 34

I notice some of the text here seems to have reverted back to old copy. I would like to confirm this is indeed correct:

1.) CTA button in the doc linked above says: "Download on Google Play". Is this correct given that the button will open the send-to-device modal for some users? Or do we in-fact need two strings for the CTA buttons:

In the case that it opens the modal, should it say:

"Get Firefox for Android"

In the case where the modal isn't supported should it say:

"Download on Google Play"

Saying "Download on Google Play" doesn't seem to make much sense when the form opens a modal? I'm going to put both strings in the template to be safe, but it would be good to have some clarity here.

2.) Also, according to the doc these strings are no longer changing:

"See how Private Browsing works"
"See how Guest Browsing works"

This is fine by me, just want to make sure this is intentional as this doc looks like an old one to me that's been updated.

3.) Finally, the doc also says:

(Links to “Supported devices” | “What’s new” | “Privacy) 

This isn't on the new design - are these needed? And if so, where should they link to?

Comment 5

[Alex Gibson [:agibson]]

I see at the bottom CTA in the page we have these existing small links:

"Supported devices"
"Release notes"

But these are still different from in the copy doc above

Comment 6

[Troy Palmer]

Hey Alex

I'm not quite sure what the correct copy is, to be honest. Until yesterday, I hadn't touched that doc since last October. My only update yesterday was to add / make revisions to the Reading List copy. My assumption is that whatever is in the demo is most likely correct, but that's just an assumption.

Comment 7

[Alex Gibson [:agibson]]

(In reply to Troy Palmer from comment #6)
> Hey Alex
> 
> I'm not quite sure what the correct copy is, to be honest. Until yesterday,
> I hadn't touched that doc since last October. My only update yesterday was
> to add / make revisions to the Reading List copy. My assumption is that
> whatever is in the demo is most likely correct, but that's just an
> assumption.

Ok I'm going to take it as whatever is on the demo server is correct. All I'm updating from there is the reading list copy.

Thanks

Comment 8

[Troy Palmer]

Since that's all I was asked to do that's probably the safest bet for you as well.

Thanks Alex.

(In reply to Alex Gibson [:agibson] from comment #7)
> (In reply to Troy Palmer from comment #6)
> > Hey Alex
> > 
> > I'm not quite sure what the correct copy is, to be honest. Until yesterday,
> > I hadn't touched that doc since last October. My only update yesterday was
> > to add / make revisions to the Reading List copy. My assumption is that
> > whatever is in the demo is most likely correct, but that's just an
> > assumption.
> 
> Ok I'm going to take it as whatever is on the demo server is correct. All
> I'm updating from there is the reading list copy.
> 
> Thanks

Comment 9

[Matej Novak [:matej]]

I'm going to set a flag for Holly here as well, specifically to comment about the Supported devices and Release notes links.

Comment 10

[Holly Habstritt Gaal [:Habber]]

(In reply to Matej Novak [:matej] from comment #9)
> I'm going to set a flag for Holly here as well, specifically to comment
> about the Supported devices and Release notes links.

When the Android product page was designed, the rule was as follows: 
- At the top of the page, we keep the download button simple and clean, with no Supported Devices and Release Notes tertiary links around it. (http://cl.ly/image/260G1E1F330O)
- For the download space at the bottom of the page (http://cl.ly/image/0r433b0m312i) we display these tertiary links near the button. 

Because this was the decision when we design this page, we should keep these links near the CTA at the bottom of the page as they are currently unless we've had any new direction from legal or PMMs to do otherwise.

Comment 11

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

(In reply to Holly Habstritt Gaal [:Habber] from comment #10)
> (In reply to Matej Novak [:matej] from comment #9)
> > I'm going to set a flag for Holly here as well, specifically to comment
> > about the Supported devices and Release notes links.
> 
> When the Android product page was designed, the rule was as follows: 
> - At the top of the page, we keep the download button simple and clean, with
> no Supported Devices and Release Notes tertiary links around it.
> (http://cl.ly/image/260G1E1F330O)
> - For the download space at the bottom of the page
> (http://cl.ly/image/0r433b0m312i) we display these tertiary links near the
> button. 
> 
> Because this was the decision when we design this page, we should keep these
> links near the CTA at the bottom of the page as they are currently unless
> we've had any new direction from legal or PMMs to do otherwise.

Thanks Holly.

So in regard to changes to the code currently on demo[0]. The only strings we're updating is the accordion for RL/RV:

Read and save articles easily
Enjoy a more pleasant reading experience with Reader View and Reading List. Access your saved articles even when you’re not online.

[0] https://www-demo2.allizom.org/en-US/firefox/android/

Comment 12

[Alex Gibson [:agibson]]

Page is updated with final copy:

https://www-demo2.allizom.org/en-US/firefox/android/

I've also included a hidden string, "Get it on Google Play", for when we sort out what's happening with the app store badges.

Comment 13

[Matej Novak [:matej]]

(In reply to Alex Gibson [:agibson] from comment #12)
> Page is updated with final copy:
> 
> https://www-demo2.allizom.org/en-US/firefox/android/
> 
> I've also included a hidden string, "Get it on Google Play", for when we
> sort out what's happening with the app store badges.

Let's just make sure we're being consistent across properties with this line. Seems like we have three different versions:

Get Firefox for Android
Get it on Google Play
Get it free on Google Play

Consistency may be a good reason to use the badges across the board.

Comment 14

[Alex Gibson [:agibson]]

(In reply to Matej Novak [:matej] from comment #13)
> (In reply to Alex Gibson [:agibson] from comment #12)
> > Page is updated with final copy:
> > 
> > https://www-demo2.allizom.org/en-US/firefox/android/
> > 
> > I've also included a hidden string, "Get it on Google Play", for when we
> > sort out what's happening with the app store badges.
> 
> Let's just make sure we're being consistent across properties with this
> line. Seems like we have three different versions:
> 
> Get Firefox for Android
> Get it on Google Play
> Get it free on Google Play
> 
> Consistency may be a good reason to use the badges across the board.

"Get it on Google Play" is consistent with the text on the Play Store badge:

See: https://www.mozilla.org/en-US/firefox/products/

This string is for alt text, and should match whatever is on the badge image itself.

Comment 15

[Alex Gibson [:agibson]]

Ok the send-to-device widget is now incorporated on the android page and up on demo2:

https://www-demo2.allizom.org/en-US/firefox/android/

Comment 16

[[github robot]]

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

https://github.com/mozilla/bedrock/commit/66b80ea42a7d6e603d86dcd9743217e78189be96
[fix bug 1139716] Android product page spring updates

https://github.com/mozilla/bedrock/commit/94a99da1334ca32de1661a65fffcf5c47348c6cf
Merge pull request #2899 from mozilla/bug-1139716-update-android-product-page

[fix bug 1139716] Update Android product page to add Reading List

Comment 17

[Alex Gibson [:agibson]]

This is now on prod: https://www.mozilla.org/en-US/firefox/android/

We still need to flip the following waffle switches:

* android-spring-updates
* firefox-android-optimizely