666671 - Redesign Mobile Download Workflow on Mozilla.com

Status: VERIFIED FIXED

(www.mozilla.org :: General, defect)

Description

[Caitlin Looney]

We need to make it easier for users to download Firefox for Android  and Firefox Home for the iPhone. We discussed merging the best elements of /mobile and mobile/download. 

Jason Grlicky also provides some great insights: "tl;dr - should we consider separating Firefox for Mobile and Firefox Home as products, so we don't even need /mobile/download?

The question is: Why is this a two-step download flow?

The bigger question is: Why is Firefox Home being shown to users who clicked the button to download Firefox for Mobile?

One answer is that right now mozilla.com treats Home like a sub-product of Mobile. From what I remember hearing, Home is slated to become its own top-tier product in the near future.  If the Home info wasn't on /mobile/download, we wouldn't even need the page. We can't cut it just yet though, since Home's product page isn't linked from anywhere else. Maybe making our top-tier product pages more consistent with each other would yield the best results here.

I think it would be worthwhile to assemble a cohesive strategy for how we'll present our top-tier products (Desktop, Mobile, & Home) on mozilla.org. This is definitely something we'll have to address in the upcoming .com/.org merge, and it's not too soon to start the discussion… so I'll dive right in and kick things off with an initial (lengthy) proposal:

For each of these products, it makes sense to keep the download experiences as simple and consistent as possible. Of course, we also want to make sure to inform the user about what they're looking at before they click Download. Striking the right balance is going to be key.

One path towards this consistency would be to model Firefox for Mobile and Firefox Home's landing page on the current Desktop download page. This page has had a lot of time to evolve, and has more research behind it than any other page on the site, so it's got to be doing something right! Like this page, there are some important elements we'd want to make sure we have on each top-tier product page:

1) Introductory text/explanation - this could be pretty short, like in a well-known product like Firefox. For Firefox Home, we'll clearly need more explanation.

2) Graphic - to clearly depict what the user is getting if they click the download button

3) Big Green Button™ That Just Works - this means using UA detection like we do on the desktop page. We'd guess the user's operating system, with a link to the supported systems if we guess incorrectly.

4) One click to get to other products - make it easy for people to explore what we have to offer

The third element is the part that this bug concerns. If we promote Firefox Home to a top-tier product, then let's put it on its own page, and remove it completely from /mobile. As for the desktop builds and beta builds, let's treat them like Firefox for Desktop does, and keep them 100% away from the mainstream download flow - I really like the idea of  separate "Developers" and "Future Releases" pages.

Ideally we could apply this level of consistency through every aspect of how we treat our products on mozilla.org - from release notes to download buttons to site navigation. Of course, if you guys have already discussed this, feel free to bring me up to speed. Either way, I think this type of discussion is going to be our greatest aid in keeping such problems from creeping in to the site design."

We currently have redirected /mobile to mobile/download as a quick and dirty "bandaid." For Q3, we'd like to see a new page that merges these two principles. 

Thanks

Comment 1

[mcbmoz]

Jaclyn,

Just noticed you weren't cc'd, adding you. Add your thoughts or close up as a dup?

Best,
C

Comment 2

[Jaclyn Fu]

Thanks for adding - 

Clarification question: was this already fixed because /mobile is now the download page (with both Android and Home)?

Comment 3

[mcbmoz]

(In reply to comment #2)
> Thanks for adding - 
> 
> Clarification question: was this already fixed because /mobile is now the
> download page (with both Android and Home)?

Yep! Closing as fixed!