1202327 - first page of www.m.o content on Firefox iOS is a non-functional download tab and an Android icon

Status: RESOLVED WONTFIX

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

Description

[:Atoll]

Attachment: As seen on TV

When I open www.mozilla.org using Firefox for iOS, one-third of the displayed page is two Mozilla logos, one third is a Download button that doesn't work ("Firefox is coming soon to iOS!", and one third is an Android logo.

While the first may be an unfortunate consequence of branding decisions, the second is incorrect (I'm *using* Firefox iOS to view the page, why would I download it again?) and the third is off-topic (I'm on iOS, why do I see an Android icon?).

Comment 1

[Richard Newman [:rnewman]]

Web devs: let me know if you need a link to an Aurora build that you can run on device to test. 

Our UA is the FxiOS/ one that you should be seeing in your analytics. Let me know if you need a more precise definition, or to find a non-UA approach.

Comment 2

[Karen Rudnitski [:kar]]

NI-ing Mike for visibility

Comment 3

[Alex Gibson [:agibson]]

Generally we don't put UA specific promo tiles on the mozorg home page. Regardless of the device you visit the home page on (iOS, Android, Firefox, Chrome) you will currently see the same content. 

The only thing we currently do on the home page is show different promos based on the locale/language of the page. The download buttons also have UA specific logic (which is handled site-wide).

This is something we could always look toward doing in the future, but we need to take into account the knock on effect this would have with regard to l10n given that the home page is translated for so many languages.

Comment 4

[:Atoll]

If the first two tiles were hidden, would the remainder of the page be valuable content? Would hiding those two tiles have an l10n burden?

Comment 5

[Alex Gibson [:agibson]]

(In reply to Richard Soderberg [:atoll] from comment #4)
> If the first two tiles were hidden, would the remainder of the page be
> valuable content? Would hiding those two tiles have an l10n burden?

We would probably have to find something to replace the first tile, as the layout changes depending on viewport size (e.g. on the iPad as opposed to iPhone). As for the second tile, this changes frequently, and can also differ depending on the locale of the page depending on which strings are translated.

Comment 6

[Alex Gibson [:agibson]]

Sorry got cut off mid-way through my reply,

So, we *could* try and just hide things, but it may start to get complicated to maintain a consistent layout given the content regularly changes and can differ per-locale. It would be nicer to have some kind of fallback content for situations where we may want to not show something after the page has rendered.

Comment 7

[Jennifer Bertsch [:jbertsch]]

Hi Richard-

Thanks for opening up this conversation.

As an Aurora build iOS user, you represent a pretty small use case among visitors to the www.mozilla.org homepage, and we don't have the bandwidth to customize the view of the page for this user group.

Thanks,
Jen

Comment 8

[:Atoll]

Sure thing.

Comment 9

[Richard Newman [:rnewman]]

Jennifer: this affects released Firefox for iOS, not just Aurora.

mozilla.org is literally the first tappable home screen tile on the front page of the browser; we should put our best foot forward here.

My mention of Aurora is only because — unless you're in Australia, Austria, or New Zealand — you won't be able to install the released version just yet because of our staged rollout. The rest of the world should be following in about two weeks. "Aurora" in this case just means non-App Store.

What kind of projected usage would you need in order to prioritize making the front page for iOS users look less like a paean to Android?

Comment 10

[Karen Rudnitski [:kar]]

Hi Jen - 

This is a pretty big deal, and we're marching towards a global release which will have marketing spend, a ton of paid & owned promo behind it, and PR coverage. In the product, we wanted to promote mozilla.org as one of the first links a user sees, and for it not to be responsive for the major platform that is iOS is likely pretty important.

What do we need to do to ensure this is prioritized accordingly before the global release? Timing should be discussed offline (ping Mike or Maria for the latest).

Thanks!

(also NI-ing Mike for visibility)

Comment 11

[Craig Cook (:craigcook)]

The download promo currently points to the "coming soon" newsletter signup in iOS browsers, but that will be updated for the global release to link to the App Store. The current Android promo is just a promo, and is shown equally to all visitors, regardless of browser or platform. We'll be changing that to an iOS promo for the global release, and then eventually changing it to something else down the road. These promos change frequently and you're just seeing the same content everyone else sees, it isn't tailored for any specific browser/platform combination.

Comment 12

[Jennifer Bertsch [:jbertsch]]

(In reply to Karen Rudnitski [:kar] from comment #10)
> Hi Jen - 
> 
> This is a pretty big deal, and we're marching towards a global release which
> will have marketing spend, a ton of paid & owned promo behind it, and PR
> coverage. In the product, we wanted to promote mozilla.org as one of the
> first links a user sees, and for it not to be responsive for the major
> platform that is iOS is likely pretty important.
> 
> What do we need to do to ensure this is prioritized accordingly before the
> global release? Timing should be discussed offline (ping Mike or Maria for
> the latest).
> 
> Thanks!
> 
> (also NI-ing Mike for visibility)

Hi Karen-

It would be helpful to understand the goal of having the www.mozilla.org homepage as the first tappable home screen tile on the front page of the browser.  The content on the homepage changes with some regularity and creating a content hierarchy based on user device and browser adds a level of complexity to homepage content management that we aren't currently set up to manage.

Maybe it would make more sense to put another www page in that spot that will better meet the goal of promoting Mozilla as the first tappable homescreen tile?  For example:
About Mozilla https://www.mozilla.org/en-US/about/
Manifesto https://www.mozilla.org/en-US/about/manifesto/
Privacy Principles  https://www.mozilla.org/en-US/privacy/principles/

Is there another promo on the current homepage that you feel would be a better fit for iOS users to see first?  Do we then distinguish between iOS users on Firefox vs iOS users on other browsers?

Could you also please share a screenshot of what that first tappable home screen tile for a new user?

We definitely want to support your team in creating a great experience for Firefox users on iOS.

Thanks,
Jen

Comment 13

[Karen Rudnitski [:kar]]

Hi Jen,

We chose mozilla.org because that's what we use on Android and is the main page for our company (if you want to see what the Top Sites looks like on default, just grab another Firefox version that you don't already have on your phone and check it out, ie beta, aurora or nightly since I'm assuming you're running release??)

We could certainly look at using another page, but obviously don't want to lose out on co-marketing our own org and any front-page news that we'd have there. Probably the best candidate would be /about/ if we had to go down that path. Obviously the least amount of work on your side, but likely the least risky in terms of timing?

We could always switch it back to the top-level when we have a better system in place to detect, no doubt.

Comment 14

[Jennifer Bertsch [:jbertsch]]

(In reply to Karen Rudnitski [:kar] from comment #13)
> Hi Jen,
> 
> We chose mozilla.org because that's what we use on Android and is the main
> page for our company (if you want to see what the Top Sites looks like on
> default, just grab another Firefox version that you don't already have on
> your phone and check it out, ie beta, aurora or nightly since I'm assuming
> you're running release??)
> 
> We could certainly look at using another page, but obviously don't want to
> lose out on co-marketing our own org and any front-page news that we'd have
> there. Probably the best candidate would be /about/ if we had to go down
> that path. Obviously the least amount of work on your side, but likely the
> least risky in terms of timing?
> 
> We could always switch it back to the top-level when we have a better system
> in place to detect, no doubt.

Hi Karen-

I like the idea of switching to the about page - it is more informational than promotional (as the homepage is) and will be getting a really strong redesign in Q1 2016.

Thanks,
Jen

Comment 15

[Karen Rudnitski [:kar]]

Thanks, Jen.

Filed bug 1204452 and bug 1204453 for default thumbnail and bookmark respectively.