Everybody Hates Firefox Updates
evilbrainjono.net
Everybody Hates Firefox Updates
1–10 of 205 posts
Re: Everybody Hates Firefox Updates
#2> I have another theory, too: When software companies get to a certain size, they start taking their users for granted. They start treating their users as pawns in a battle against some other company. Faceless millions. Gotta copy everything the other company does, or risk falling behind. So they end up doing everything the other company does whether the users want it or not, and probably doing a crappy job to boot.
> In our case, we started thinking of everything in terms of the battle against Google Chrome. Oh no, Chrome is doing such-and-such; we'd better do something equivalent or we'll fall behind! We thought we needed a rapid update process like Chrome. We were jealous of their rapid update capability, which let them deploy improvements to users continuously. We had to "catch up" with Chrome's updating capability.
> Credit where it's due: the way Google handled Chrome updates was very, very smart. They recognized that updates are one of the hardest things to get right, so they solved that problem first, before releasing version 1. The first release of Chrome was little more than an empty box of a browser, but it was wrapped around an excellent updating system. This let them gradually transform that empty box into a full-featured browser, without the users ever realizing they were getting updates.
> Firefox did not do such a good job with rapid releases. I've written before about the specific mistakes we made, so I won't go into detail again. To summarize: we did the updates in a very intrusive way, requiring lots of user attention, which made people annoyed because it happened so often. When people restarted after an update to find no visible difference, they wondered what was so important about that update. (Remember the rule that the benefit of the update needs to outweigh the pain? We broke that rule.) Worse yet, we didn't do enough to preserve add-on compatibility, making the updates extremely disruptive to people who depended on certain add-ons; and we kept going with our old version-numbering scheme even though the meaning of the numbers had changed completely, leading to mass confusion.
This reminds me of certain OS races: Microsoft trying to upgrade its 16-bit, cooperative multitasking Windows 3.1, and then ditching it for a new model based on NT, while Apple flounders with the Mac OS's 6 to 9, until it finally got a reasonable architecture with OSX - leading to Microsoft floundering with Vista. But the problem here is the opposite - the difficulty in competing is the same, but the two companies were reluctant to recognise the edge the competitor's system had on theirs until it was costly to fix.
Re: Everybody Hates Firefox Updates
#3"After years of aspiring to improve software usability, I've come to the extremely humbling realization that the single best thing most companies could do to improve usability is to stop changing the UI so often!"
I wish I could ink this command onto the right hand of programmers (and program managers) everywhere.
Re: Everybody Hates Firefox Updates
#4Re: Everybody Hates Firefox Updates
#5The takeaway quote: "After years of aspiring to improve software usability, I've come to the extremely humbling realization that the single best thing most companies could do to improve usability is to stop changing the UI so often!" I wish I could ink this command onto the right hand of programmers (and program managers) everywhere.
Re: Everybody Hates Firefox Updates
#6This just isn't true. In a web browser, sure, the UI barely matters. Going through the menus in Firefox or Chrome is rare, enough so that Chrome tends to look different every time I do it.
But for real programs, the UI defines the workflow, and that should be optimized, even at the expense of familiarity. Just be sure that it actually IS better.
So yes, the quoted advice should probably be considered and possibly adopted by FireFox and maybe Chrome. But desktop software shouldn't accept it without a huge dose of salt.
Re: Everybody Hates Firefox Updates
#7The problem isn't about 'rapid release cycles', but about the UX design of the update process. Even before the rapid release cycles, Firefox would check for add-on updates every time it was started. Chrome's update mechanism is completely seamless and invisible and requires zero user attention.
Re: Everybody Hates Firefox Updates
#8So, note to developers: Frequent updates drive your infrequent users crazy.
Re: Everybody Hates Firefox Updates
#9I hate firefox updates because I use it infrequently enough that I have to update just about every time I open it. Also on this list is my Playstation3, which wants me to do system update and a software title update on the rare occasion I try to use it. Makes me not even want to turn the thing on. So, note to developers: Frequent updates drive your infrequent users crazy.
Re: Everybody Hates Firefox Updates
#10The takeaway quote: "After years of aspiring to improve software usability, I've come to the extremely humbling realization that the single best thing most companies could do to improve usability is to stop changing the UI so often!" I wish I could ink this command onto the right hand of programmers (and program managers) everywhere.