Firefox Appears Ready to Crack 20% Share Next Month
CWmike writes "Mozilla's Firefox browser is on pace to hit the 20% market-share mark next month. Net Applications marketing VP Vince Vizzaccaro didn't pin all of Firefox's increase on a change last month to its update dialog; he did note the new approach. 'Mozilla has implemented a change in Firefox 3.0 [Release Candidate 1] where the installation now has a checkbox that defaults to making Firefox your default browser,' he explained. He refused to ding Mozilla for the practice. 'The option is clearly displayed and labeled, unlike Safari, which misleadingly labeled the Safari install as an "update" [but has] since correctly changed to an 'install.' However, this practice is a break from the traditional practice browsers employed of defaulting this option to off.'"
What does the "default browser" setting actually do? I always run the browser by clicking the "firefox" icon (or "internet explorer," if necessary). So I don't see when the "default browser" is invoked.
Firefox @ 16%
Firefox @ 18%
Firefox @ 40%
So which one is right?
However, this practice is a break from the traditional practice browsers employed of defaulting this option to off.
Odd. Nearly every browser I've used warns me that it's not the default if I've set something else to be the default. I don't recall going into every single one of those and turning the "check if this browser is the default" option on.
I've seen specific cases where, unfortunately, a programming team ignored the firefox angle when testing their code, and wrote in .NET specific goodies that only worked in IE.
Sure enough, sales dipped almost 20% for a week. We ran the reports, and Firefox was accounting for 21% of site traffic (until that week, where it dropped off to almost nil). We quickly fixed the code, and firefox shot right back up to 21-22%.
The demographics for this website are a little bit younger than the general population, so it made sense that we had already broken through 20%
davejenkins.com |
I mean, most people that go out of their way to download a browser installer probably intend to use that browser as their default, whether it's Safari, Opera or Firefox.
Picture this: Joe User downloads and installs Firefox, clicks right through the installer without reading and then starts clicking the little Firefox icon when he wants to surf the net. However, since the 'default' checkbox was blank by default, whenever his friend on MSN sends him a link, he clicks it and it opens in Internet Explorer. In my experience, a very large number of users will not notice that they're not in their usual browser for quite a while. They may navigate away from the linked site and do banking or other security sensitive stuff, but now they're in a browser that hasn't necessarily been keeping up with patches because it's rarely being run.
I don't know, but it seems to be that it's safer to default that box to be checked. Users that keep multiple browsers for testing purposes already know to look for it, will remember to uncheck it, and are in the minority anyway.
Why is it that web designers and developers - and I'm guilty of this too - almost always knowingly use a browser that most of their users won't? I guess it's not so much of a problem anymore, but back in the day developing in Firefox, Opera, or any browser that wasn't IE was a sure way to run into interesting and convoluted issues when your users views your page in IE and it renders all differently.
There's actually quite a lot to be said for asking certain questions when an app starts rather than at installation time.
The questions you ask at installation time should be the ones that sysadmins can answer, like where do you want me to put the app and which components do you want to install.
The questions you ask when a user starts the app (for the first time) are questions that the user's answer. An easy way to work out which category a particular choice falls in is whether or not the setting is per user or one setting for the entire machine.
The default browser is a per user setting and the choice should be offered when a user starts the app for the first time.
Presumably what Mozilla have done is to set the default browser for the user performing the installation. This seems somewhat perverse.
Of course Mozilla has little penetration in corporations where these issues are more relevant. And it won't ever get any such penetration until there are good tools for packaging Firefox + add-ons in an MSI. Before anyone flames about MSI being Windows only, corporations overwhelmingly use Windows on the desktop. And even for non-corp users I'll bet Firefox gets more use in Windows than the other OSs combined.
I'm really getting tired of firefox crapping out on me (usually because of flash it has to be said) and because its running one big multi threaded app no matter how many windows you open or seperate instances you attempt to start, the whole lot disappear taking all my sessions with them. The current multi process option doesn't work. Have they added one yet that does because it really needs it if they can't sort out the reliability?
Presumably they make it multi threaded so it fits into Windows limited process model but surely a multi process version can't be hard to achieve!
That comment isn't informative, its inquisitive, which should be a mod option.
Well.. maybe. Or Maybe not. But Definitely not sort of.
Maybe with 20% market share I will start meeting web site designers who know that Microsoft is not "the internet", that there are other browsers and that the W3 sets the standards.
Would having 20% of the share of the browser market make Firefox the most successful *end user* FOSS?
If so, I think it provides a loud message to old school free(dom) software developers who see crappy interfaces as only a small inconvenience that users SHOULD suck up and stop "whining" about.
IMHO one of the reasons for the success of Firefox among Jane User is the easy of use and simple interface.
Where, and when are we getting to see the browser usage distribution of Slashdot?
I bet you could have one of those stories with more than 1000 posts by publishing it in the "Taco Blog", and linking to it.
It would probably be very interesting to see how (if?) the distribution varies depending on section (games, linux, mac etc).
I run a fairly busy site that has the following stats:
1. Internet Explorer 97,589 75.07%
2. Firefox 26,383 20.30%
3. Safari 4,844 3.73%
4. Opera 500 0.38%
5. Netscape 329 0.25%
6. Mozilla 270 0.21%
7. Konqueror 37 0.03%
8. Camino 21 0.02%
9. Mozilla Compatible Agent 6 > 0.00%
10.
Playstation 3 5 > 0.00%
What is interesting to note is that this site is for stock investors so think middle aged, none-technical crowd.
(Com-on Konqueror!)
You could also check out Emesene. It's fairly new to the scene, but looks promising.
Today is red jello day - all workers must eat all of their red jello. Failure to comply will result in five demerits.
I use primarily Firefox during web development, because it seems more efficient and sensible to target a reasonably compliant browser first, and then adjust to IE afterward. I use Firefox mostly because having Firebug available is so useful during development and debugging.
Personally I prefer using command line FTP to download Firefox on windows machines. That way I never have to use Internet Explorer. On Linux I just urpmi (or whatever your distro uses) to get firefox.
Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.