1074291 - Consider simplifying download steps in release-notes sidebar

Status: RESOLVED WONTFIX

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

Description

[Steven Garrity [:sgarrity]]

Attachment: Screenshot 2014-09-29 14.22.49.png

While discussing the download links for mobile visitors on the Release Notes sidebar (Bug 1061715), I began to wonder if this 1/2/3/4 numbered list on the sidebar actually makes sense.

The attached screenshot shows the steps. This is an example of the page in question:

https://www.mozilla.org/en-US/firefox/32.0.3/releasenotes/

1. I think a 4-step process to try Firefox makes the first impression a bit daunting. A singular "Try Firefox" call-to-action might be more appealing.

2. If a visitor clicks the first link ("Check >>") in list, they are taken to a support.mozilla.org page with system requirements. I think for most people, we will have lost them by now.

I tend to think we might do better if we simply direct people to /firefox/new/ like all of our downloads.

Please keep in mind that release notes can be for either mobile or desktop releases, which complicates the logic behind the "Check >>" and "Install >>" we have now.

Comment 1

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

Below is the recommendation for updates to the release notes template:

# Remove the "step" box entirely.
# Replace the step box with a download button
- on desktop page: show button when user is viewing from desktop
- on desktop page: hide button when user is viewing from mobile
- on mobile page: always show Google playstore download button
# Add a white content box under the new download button
# Title of the content box will be "Also try:"
# The new content box will contain 3 links
- Customize
- Get Involved
- System Requirements

Reference:
Mobile - https://www.mozilla.org/en-US/mobile/32.0/releasenotes/
Desktop - https://www.mozilla.org/en-US/firefox/32.0.3/releasenotes/

Comment 2

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

Waiting until the refactor of the release notes section is complete before implementing this change.

Comment 3

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

(In reply to Cory Price [:ckprice] from comment #1)
> Below is the recommendation for updates to the release notes template:
> # Replace the step box with a download button

The current layout has a link to ">> Download" that sends the user to /firefox and either shows the download, or if the user is updated a "you're up to date" message.

A couple options here

1. Show a download button (using this creative - http://cl.ly/image/0b34031m1r0d) that will link to firefox/new for desktop, and the Play store for mobile.
2. Attempt to do the version-checking on the page, and show the button, or appropriate "you're updated" copy.

I am leaning toward option 1.

Thoughts?

Comment 4

[Holly Habstritt Gaal [:Habber]]

(In reply to Cory Price [:ckprice] from comment #3)
> (In reply to Cory Price [:ckprice] from comment #1)
> > Below is the recommendation for updates to the release notes template:
> > # Replace the step box with a download button
> 
> The current layout has a link to ">> Download" that sends the user to
> /firefox and either shows the download, or if the user is updated a "you're
> up to date" message.
> 
> A couple options here
> 
> 1. Show a download button (using this creative -
> http://cl.ly/image/0b34031m1r0d) that will link to firefox/new for desktop,
> and the Play store for mobile.
> 2. Attempt to do the version-checking on the page, and show the button, or
> appropriate "you're updated" copy.
> 
> I am leaning toward option 1.
> 
> Thoughts?

Agreed for option 1 since we can implement immediately. 

We do need to address providing more specific status messaging like "you're up to date" across mozilla.org wherever our buttons exist (not just on /new), but we can take that on as a separate project. We shouldn't let that block this bug at the moment. 

My goal is that as part of how our download buttons are implemented on mozilla.org, this status messaging would be automatically displayed for the user and work no matter what page layout the button is on.

Comment 5

[Jennifer Bertsch [:jbertsch]]

+1 to Holly's comments in #4.

Closing since we are moving on to a new release notes design.