Closed Bug 1027318 Opened 6 years ago Closed 5 years ago

Download button should offer a Firefox Refresh option before download of the same Firefox version

Categories

(www.mozilla.org :: Information Architecture & UX, defect)

Production
defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: verdi, Assigned: jpetto)

References

(Blocks 2 open bugs)

Details

(Whiteboard: [kb=1415033] [fxgrowth])

Attachments

(4 files, 3 obsolete files)

Problem: You determine that there is an issue with Firefox and in an attempt to fix it, you download and re-install the same version of Firefox that you already have on your computer. Re-installing Firefox doesn’t fix very many issues. In almost all cases it doesn’t seem to do anything at all. This is contrary to users’ expectations. The procedure that you actually want in this case is Firefox Reset.

Offering the reset option before downloading Firefox fits into the common repair procedure of re-installing problematic software and by offering it before the user re-downloads, it directly addresses the problem without the added time and bandwidth of downloading and installing.

We'd like the Firefox Download button to offer an option to reset Firefox when a user is about to download the same version of Firefox that they are already using (e.g. using Fx 30.0 to download Fx 30.0). 

More background: http://people.mozilla.org/~mverdi/mockups/reset/reset2014v2.pdf
Component: Bedrock → Information Architecture & UX
Thanks for filing, Michael.

I'm going to ask Holly to consider this as an enhancement to the /new page and/or part of the download button testing she's working on.

Holly - I'll put time on the calendar to discuss.
Whiteboard: [kb=1415033]
Hi Michael, 
See the following bug which talks about allowing the web to know the status of a silent update so that we can provide information like this. 

https://bugzilla.mozilla.org/show_bug.cgi?id=998962
I like Michael's idea for attaching a message to the download button itself or altering the button area somehow to display this information. If the /new page has this information and is whitelisted we can, as a minimum, provide a conditional message saying the user can restart, as well as not display an unnecessary download button.
Depends on: 988725
Attached image mozorg-w-reset-button.png (obsolete) —
After running though a few iterations with the Firefox UX team, we thought a better solution would be to show a reset button instead of download button. There would still be a link to download for people who need it.
Attachment #8442401 - Attachment is obsolete: true
Attachment #8442402 - Attachment is obsolete: true
Whiteboard: [kb=1415033] → [kb=1415033] [fxgrowth]
No longer depends on: 988725
cmore, wasn't sure if this was on the firefox growth team's radar.
Flags: needinfo?(chrismore.bugzilla)
(In reply to Mike Alexis [:malexis] from comment #6)
> cmore, wasn't sure if this was on the firefox growth team's radar.

Yes, mverdi is working on it. We are adding [fxgrowth] to the whiteboard on any bugs that we are working on for the growth team.
Flags: needinfo?(chrismore.bugzilla)
Summary: Download button should offer a reset option before download of the same Firefox version → Download button should offer a Firefox Refresh option before download of the same Firefox version
Is the web-side of this feature being worked on for the Firefox 35 time-frame?
Flags: needinfo?(mverdi)
(In reply to :Gavin Sharp [email: gavin@gavinsharp.com] from comment #8)
> Is the web-side of this feature being worked on for the Firefox 35
> time-frame?

Yes. Jon Petto, Alex Gibson and I talked about this yesterday and ironed out what needs to be done.
Flags: needinfo?(mverdi)
Assignee: nobody → jon
Do we have a link destination for the "How does refreshing Firefox work" link underneath the button?
Flags: needinfo?(mverdi)
(In reply to Jon Petto [:jpetto] from comment #10)
> Do we have a link destination for the "How does refreshing Firefox work"
> link underneath the button?

https://support.mozilla.org/kb/reset-firefox-easily-fix-most-problems
Flags: needinfo?(mverdi)
To summarize what we discussed in PDX:

On /firefox/new/, we will use the UITour to check the user's point release and update channel. If the user's version matches the latest version and their update channel is release, we will show the refresh button.

Existing functionality will remain untouched on /firefox/new/. The page currently checks if the user is on the latest major version, and, if so, displays an up to date message and hides the download button.
Attached file GitHub PR
Can the strings in this bug be considered final?
Yes, I believe the three new strings present in the PR are final:

"Refresh Firefox"
"Fix problems and restore performance"
"Learn more"
Attached image refresh-mozilla.org.jpg
I'm sorry - that is an old mockup. The strings should be:
"Give Firefox a tune up"
"Refresh Firefox"
"Learn more"

If it helps, "Give Firefox a tune up" and "Refresh Firefox" are the same strings, used in the same way as the ones on about:support.
Attachment #8483013 - Attachment is obsolete: true
Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/e22a12dcee78005464e8b55bfc5cbeab43abb9c9
Add refresh button UI to /firefox/new/. Bug 1027318.

- Add minor JS optimizations.
- Remove GA experiment snippet (no longer used).

https://github.com/mozilla/bedrock/commit/6ff1b70d6112a5708e2c7dc25464b73dabb5b13e
Merge pull request #2628 from jpetto/bug-1027318-firefox-new-refresh-button

Add refresh button to /firefox/new/. Bug 1027318.
Nice job everyone on getting this live!

:jpetto: is there a GA event set when a user clicks the "refresh Firefox" button? If not, we should add that so that we know how many users take the action.
Flags: needinfo?(jon)
If we don't have event, we should use the "/new Interaction" category like we have on the rest of the in-page interactions that we have tagged.

Garethc: ^^
Flags: needinfo?(garethcull.bugs)
Yes cmore. That would work. Please use /new Interaction event category. Could we please track the button click with the following:

_gaq.push(['_trackEvent', '/new Interaction', 'Refresh Firefox', 'Firefox Desktop']);

Thanks
Flags: needinfo?(garethcull.bugs)
Attached file GitHub PR
Submitted PR to add GA tracking to the refresh button.
Flags: needinfo?(jon)
Should we add tracking for when the refresh button is displayed as well? If so, should the PR submitted in comment #21 wait for that tracking to be decided upon?
(In reply to Jon Petto [:jpetto] from comment #22)
> Should we add tracking for when the refresh button is displayed as well? If
> so, should the PR submitted in comment #21 wait for that tracking to be
> decided upon?

Can you add when the refresh button is displayed and hold that PR until we get that in? That's how we are going to measure conversion rate. We could guess on when it is displayed, but it isn't fool proof.
Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/704f5150ff7ab09d1e67e803d98c8c57dcd05314
Add GA tracking to Fx refresh button. Bug 1027318.

https://github.com/mozilla/bedrock/commit/31d8c08d3a02dd2daebc1d0c58158fc40103a54c
Merge pull request #2658 from jpetto/bug-1027318-add-GA-firefox-refresh-button

Add GA tracking to Fx refresh button. Bug 1027318.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.