Closed Bug 542589 Opened 16 years ago Closed 16 years ago

Provide different FF 3.6 Major Update prompt screen for users coming from Firefox 3.0.8

Categories

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

Product:
www.mozilla.org
Component:
General
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: dveditz, Assigned: jslater)

References

Details

When 3.0 users get a "Major Update" prompt to 3.5 currently they see a straight-forward positive marketing message for the next version http://www.mozilla.com/en-US/firefox/3.5/details/ As we move toward 3.0.x EOL we need to start ramping up the scary -- your version will soon be unsupported, stay safe and upgrade. Please to be writing new marketing text for that screen. kkovash has some feedback from the most recent 3.0 Major Update that we also should incorporate. The sooner the better. We'd like to do another major update from the upcoming 3.0.18 to be released mid-February, and we'll need time to localize the text. One potential complication is that we will probably do the major update from 3.0 to 3.6, jumping over 3.5, which means as currently set up users will get the text from http://www.mozilla.com/en-US/firefox/3.6/details/ This currently is also used as the text for a 3.5 -> 3.6 major update. Scary "support is ending, you'll be vulnerable" text might not be appropriate for 3.5 users (or maybe it is). We could point the two versions at different URLs, but if that's the plan make sure Release Engineering knows because they may need to tweak their scripts that generate the update snippets.
Summary: Update FF 3.0 Major Update prompt screen → Re-write FF 3.0 Major Update prompt screen
Ok, I think I understand, but please let me know if this is the correct set of assumptions: - we need some scary "upgrade now" text to prompt 3.0 users to move to 3.6. - 3.5 users should see the existing, non-scary 3.6 upgrade promo, so no new writing is needed, but we'll need to work with RelEng to make sure that the right people are directed to the right version. If that's correct, I can do this in the next day or two. If it's not, then please let me know what I've missed. Ken, can you share the insights mentioned in comment #0?
(In reply to comment #1) > Ken, can you share the insights mentioned in comment #0? I'll leave him to comment more thoroughly of course, but one of the ones that really surprised us was that many users who declined the update offer did so because of questions about cost. We should fix our language to make the freeness of updates more explicit, it would seem.
I'll have a blog post tomorrow with the full data, analysis, and suggestions.
My blog post is now live -- http://blog.mozilla.com/metrics/2010/01/28/why-people-dont-upgrade-their-browser-part-iii/. I've made suggestions for changing two of the bullet points within the /details page... not sure if there's anything fancy we should do from a design/creative perspective other than simply modifying the text.
Ok, my first pass at the text for this is below...take a look and let me know what you think. I'm happy to revise as needed. Ken's blog post was a big help, so between that and the comments above I tried to emphasize the urgency of the need to update plus the concepts of free, stable and easy. The tricky part is that there's not a lot of room (I based the format on http://www.mozilla.com/en-US/firefox/3.6/details/ - let me know if that's an incorrect assumption), so brevity is really crucial. Anyway, here's the text: Security Warning! _Please update to Firefox 3.6_. * Includes essential security fixes. * Faster browsing and fewer crashes. * Updating is easy and always free! Also, as an added bonus here's a slightly different version (which includes "free" in the subhead, but makes the call-to-action a bit less clear...I prefer the first version to this one): Security Warning! _Free update to Firefox 3.6_. * Includes essential security fixes. * Faster browsing and fewer crashes. * Updating is easy and always free! Lastly, a devil's advocate question...we can't say anything like "Update Required" in the headline can we? I'm assuming not, but that would certainly be attention-getting (and then we could focus on "free" in the subhead).
(In reply to comment #5) > Lastly, a devil's advocate question...we can't say anything like "Update > Required" in the headline can we? I'm assuming not, but that would certainly be > attention-getting (and then we could focus on "free" in the subhead). I don't really see why not, tbh. I know you want to avoid overstating things, but an update *is* required in order to stay safe long term, and if you think that language will be more persuasive, I don't think there's anything dishonest or inappropriate about using it. If this was the first major update for 3.5, not a last ditch attempt, I think I'd want us to be more positive about the reasons people should move, but once we get near end of maintenance, I think it's appropriate for the messages to become more dire, within reason. FWIW, I definitely prefer the second subhead text, where we are explicitly offering a "Free update to Firefox 3.6." I think at that point we could even liberate the third bullet point for another feature sell ("easier than ever to personalize"?) but I'll try not to bikeshed the language too much, just wanted to express the preference.
Thanks Johnath - that's helpful. Below are two more versions based on your feedback: Update Required! _Get the free Firefox update_. * Includes essential security fixes. * Faster browsing and fewer crashes. * Keeps your existing Firefox settings. Security Warning! _Update to Firefox 3.6 (free)_. * Includes essential security fixes. * Faster browsing and fewer crashes. * Keeps your existing Firefox settings. Notes: - I tweaked the subheads a bit so they'd both start with a verb. I think it's a stronger CTA that way. - good call on the last bullet, but I think the fact that you retain your info from the previous version of Fx is a stronger immediate message for these folks than personalization/personas (which is conveyed on the 1st run page). Comments are encouraged!
(In reply to comment #7) > Update Required! > _Get the free Firefox update_. > > * Includes essential security fixes. > * Faster browsing and fewer crashes. > * Keeps your existing Firefox settings. Beltzner can be relied upon to have an opinion here that is both brilliant and dripping with context, but for all of that - I wouldn't change a word here. Really good call on the "keeps your existing settings" bullet.
Sounds good to me! I'm happy with that text. What's the next step to get this implemented?
The one thing that may be missing from all these versions is that support for 3.0.x is ending. It's maybe implied by the fact that 3.6 contains "essential" security fixes, but I wouldn't mind a more explicit "Support for Firefox 3.0 is ending, upgrade to remain secure" kind of message. For an example see http://www.mozilla.com/en-US/firefox/3.0/details/ Firefox Security Alert! Immediate upgrade recommended. * Your current browser is no longer supported. * Upgrade to Firefox 3 to stay secure. That's a little strong for the current 3.0 state, but we had similar "will soon be no longer supported" sort of text for the penultimate release. Or maybe it will be accurate -- is 3.0.18 the last one or will there be a 3.0.19? That might depend on how motivational the text is.
To be clear I'm not recommending anything like the exact text we used above -- the one and only message there is "upgrade already, dammit!" and includes no positive message at all. But some variant on it would be a stronger replacement for "Includes essential security fixes", accompanied by your upsell messages about speed, stability, personalization, FREE!, etc.
Yeah, those are very good points (in comments #10 and 11). The main challenge, of course, is finding the space to fit it all in...these update windows are pretty tight. As a window into my thought process, I was thinking that the concept of a browser not being supported might be a little vague to people outside the software industry, so I went with the "essential security fixes" line as an alternate way of getting at that same point. I'd be glad to keep working on this, though. Johnath, Beltzner (when you get back), what do you think?
(In reply to comment #0) > This currently is also used as the text for a 3.5 -> 3.6 major update. Scary > "support is ending, you'll be vulnerable" text might not be appropriate for 3.5 > users (or maybe it is). We could point the two versions at different URLs, but > if that's the plan make sure Release Engineering knows because they may need to > tweak their scripts that generate the update snippets. We've gotten to this point of needing an URL, so that we can generate the 3.0.18 -> 3.6 update for QA testing. How about http://www.mozilla.com/%locale%/firefox/3.6/details/from-3_0.html instead of .../index.html ?
Snippets have been generated using the url in comment #13. We can regenerate if thats's a problem.
3.0.18 will ship in about a week, and the major update from there is set to point to 3.6. What's the status with the billboard content and localization ?
(In reply to comment #15) > 3.0.18 will ship in about a week, and the major update from there is set to > point to 3.6. What's the status with the billboard content and localization ? At the delivery meeting last week we decided to wait until Beltzner had returned from vacation to get his feedback. Mike, any thoughts? My last draft was in comment #8, but dveditz raised some additional issues that are discussed after that. If you're happy with comment #8, then we can move forward. If you want to discuss the alternatives further, I'd certainly be happy to do so.
(In reply to comment #16) > If you're happy with comment #8, then we can move forward. If you want to > discuss the alternatives further, I'd certainly be happy to do so. Yup, with a small changes (s/Required/Recommended/): Update Recommended! _Get the free Firefox update_ * Includes essential security fixes. * Faster browsing and fewer crashes. * Keeps your existing Firefox settings. Pascal: if "Get the free Firefox update" is too long, drop "Firefox" out to shorten. (In reply to comment #15) > 3.0.18 will ship in about a week, and the major update from there is set to > point to 3.6. What's the status with the billboard content and localization ? I take it that those snippets were generated to point to /details/3.6/from-3_0.html as per comment 13?
Mike, do you think "Update Recommended" has a stronger get-people's-attention message than "Firefox Security Alert"? (I'm honestly asking, not poking at your edit) I totally understand your hesitation to call it required, but want to make sure we're doing all we can to communicate the importance of this update.
(In reply to comment #17) > I take it that those snippets were generated to point to > /details/3.6/from-3_0.html as per comment 13? They were. It's not a big deal to point them somewhere else, say if we want to use the existing 3.6 snippets for an unprompted 3.0.18 -> 3.6, then switch to new ones before making it prompted.
Blocks: 545789
No longer blocks: 515417
Mike, any final thoughts about comment #18? I'd like to make sure we're on the same page on that before we close this one out.
(In reply to comment #19) > (In reply to comment #17) > > I take it that those snippets were generated to point to > > /details/3.6/from-3_0.html as per comment 13? I missed the swapping of details and 3.6 here. The url being used is http://www.mozilla.com/%LOCALE%/firefox/3.6/details/from-3_0.html When will this content be pushed live ? In the interests of disclosure it's going to be much more painful to publish only some locales.
Blocks: 546191
(In reply to comment #21) > When will this content be pushed live ? In the interests of disclosure it's > going to be much more painful to publish only some locales. Actually, I mean that enabling the unadvertised major update for only some locales is a bit painful. Much nicer to do it all in one go, and maybe that's after the 3.0.18 release day, but we can deal.
(In reply to comment #18) > Mike, do you think "Update Recommended" has a stronger get-people's-attention > message than "Firefox Security Alert"? (I'm honestly asking, not poking at your > edit) No, I don't. I also don't think that the upgrade from Firefox 3.0.18 to Firefox 3.6 is a Security Alert at this time - we have not yet decided that we will be stopping support for Firefox 3.0.x, and I don't want to cry wolf. > I totally understand your hesitation to call it required, but want to make sure > we're doing all we can to communicate the importance of this update. We are doing all we can to communicate the importance of this update at this time. > I missed the swapping of details and 3.6 here. The url being used is > http://www.mozilla.com/%LOCALE%/firefox/3.6/details/from-3_0.html > > When will this content be pushed live ? In the interests of disclosure it's > going to be much more painful to publish only some locales. Ugh. Well, this really sucks. There's nothing at those URLs right now, so that means we can't really push the major update offer live when we ship Firefox 3.0.18, I guess.
I was a little shocked to discover that the locale that was missing this was actually only en-US, and pascal and the l10n team had been diligently translating away. I've fixed that, now: https://www-trunk.stage.mozilla.com/en-US/firefox/3.6/details/from-3_0.html Pascal/Nick: what happens if that file is 404 for a locale? do we fall back to en-US, like we do with other pages, or do we need to manually copy the english file over to make sure there's some content there?
There is already a copy of the English version in all locales folders, personnally as I told on IRC, I would prefer copying the details/index.html over to from-3_0.html for the missing locales tomorrow so as that people see an update message to 3.6 in their language, it's a lighter message but it is better than English for end-users IMO.
(In reply to comment #25) > over to from-3_0.html for the missing locales tomorrow so as that people see an > update message to 3.6 in their language, it's a lighter message but it is > better than English for end-users IMO. That's fine with me, sure.
Nothing, this seems resolved, resummarizing and marking FIXED.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Summary: Re-write FF 3.0 Major Update prompt screen → Provide different FF 3.6 Major Update prompt screen for users coming from Firefox 3.0.8
Component: www.mozilla.org/firefox → www.mozilla.org
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.