Tag: Firefox

Categories
Web Technology

Is Firefox Past its Prime?

A few weeks ago, in a post about why Google+ is going to succeed, I noted that Google Chrome has been on an upward trend of about .5–1% per month since it launched nearly two years ago.

While I didn’t mention it at the time, Firefox has an interesting usage graph as well. If you follow that link, you’ll see that Firefox’s curve hovered a little over 30% for the tail end of 2009 and the better part of 2010, but has started to drop over the past twelve months.

If these trends continue, Chrome will be more popular than Firefox by the end of next year.

What does this mean for everyone’s favourite open-source browser?

From Phoenix to Providence.

Back around 2003, the ‘net was desperate for something new. Sure there were other browsers around, but nobody could hold a candle to the market-dominating behemoth that was Internet Explorer (source). Innovation was non-existent, and the web as we knew it was suffocating.

Enter Mozilla. The release of Firefox 1.0 in 2004 was a breath of fresh air for the online community. Suddenly there was an open-source, standards-compliant competitor gaining momentum. We were thrust from the shackles of monopoly into an arms race that culminated in the second browser war.

Mozilla was a critical piece of the puzzle. It was a veritable flagship of new, exciting features. Better CSS support. A clean, tabbed interface. The prevalence and importance of add-ons could be its own post; countless extensions have become standard features across the board of popular browsers.

By the time Firefox 3 was released, in June 2008, Mozilla could do no wrong. Everything was on the up-and-up.

Then, the landscape changed.

Is Firefox still necessary?

With Microsoft innovating again (see IE9), Apple’s devices gaining popularity (and Safari with them), and Google bursting into the browser space with Chrome, competition was hot in 2009/2010.

Firefox still played a key role at this time: it was the yardstick against which all other browsers were held. Sure Safari and Chrome have built-in development tools, but are they as good as Firebug? How does WebKit’s HTML5 support compare to Gecko’s? And isn’t IE still laughably behind?

But this role has run its course. The major players are now well-established. Most users are aware of alternatives to their operating systems’ default browsers.

This can’t be a long-term position for Firefox. It won’t last.

The competition is no longer resting on its laurels. Chrome is closing in. Internet Explorer is finally in a position to reverse its eight-year downward trend, and WebKit is absolutely dominating this year’s explosive rise in mobile browsing.

Extensions are everywhere. Support for standards has never been better. Firefox is quietly becoming less and less relevant with each passing update.

So I ask again:

Does the golden age for Firefox lie in its past?

Categories
Web Misc

Elsewhere: HTML5 and Browser Testing

I wrote a couple of posts for work last week:

Hopefully those will be of interest to you if you’re into techie web stuff.

This week’s post for this blog is a bit more opinionated than usual, and is taking longer as a result. It probably won’t be up until tomorrow. But it’s going to be my first post (ever!) about copyright, which is something I can get a bit touchy about, so you don’t want to miss it.

Categories
Web Misc

Modern YouTube meets Retro Firefox

A quick bonus-Friday-post to help get your Friday rolling:

I’m doing some web development at my day job for a site that simply must work in Firefox 1. It’s not as bad as it sounds (we’re also supporting IE6, which is a far bigger hassle) and every once in a while using a really old browser provides a bit of comic relief. For example, when I accidentally opened a YouTube video using Firefox 1, here is what I saw:




(click image to enlarge)

The text reads: “Hey there, this is not a commercial interruption. You’re using an outdated browser, which YouTube no longer supports. Some features on YouTube may not work.”

How ironic that the outdated-browser warning message is nearly unreadable in outdated browsers! It looks like even the brilliant minds at Google occasionally struggle with legacy-browser support, just like the rest of us ;)

Have a good weekend!

Categories
Software Development Web Technology

Software is all about Context

Context is a very important factor in software development. Knowing the conditions under which your software will be used is an integral part of crafting a positive experience for your users. Many companies take this to heart and create truly engaging software that really connects with its users, but the vast majority miss the mark. While I’m sure I’d have no trouble pointing out a myriad of context-related issues in software made by Average Joe Developer, today’s focus will be on showing that even the top names in software aren’t perfect.

Exhibit A: The iPhone’s Clock.app

Let me tell you a story. A few weeks ago, the fiancée and I were scheduled to meet with a potential wedding venue early Saturday morning. Given that it was a bit out of the way and we tend to oversleep, we thought we’d be smart and set an alarm using the iPhone’s default clock app.

So Friday night, we set an alarm thinking it would wake us up Saturday morning. It did not; it turns out the alarm we set was for weekdays only! While this was entirely our fault, I’m still going to call Apple out on not taking context fully into account: when we set the alarm, why didn’t the app warn us that the alarm wouldn’t go off the next morning? I would imagine it’s very rare that anyone sets an alarm more than a day in advance. It’s much more likely that when someone sets an alarm at night, they expect it to wake them up the next day. This is a case where a neat feature is actually an annoyance because context isn’t handled as well as it could be.

Exhibit B: Google Maps

Continuing our story, while I was frantically trying to get ready I was loading Google Maps to get directions to our appointment. After punching in the address and asking it to route us there, Google Maps told me the trip would take over 9 hours. I freaked out! We don’t have 9 hours, we have 30 minutes; is this the right address? Did we accidentally book an appointment at a venue 9 hours out of Ottawa?

Actually, it turns out I had Google Maps set to give walking directions. Again, my fault, but again, where were the developers on this one? Did they really think I wanted to walk over 9 hours to get somewhere? Why not recognize that I was probably looking for driving directions and put a message at the top of the screen asking if that’s what I meant?

(For the curious, this story did have a happy ending: we made it there a slight 15 minutes late, and this was the venue we eventually chose for our wedding.)

Exhibit C: Firefox’s Spell-Check

Firefox is an incredible piece of software. It is currently the browser of choice for about one quarter of all internet users, and in many ways helped to revolutionize the web browser market. But one area where it hasn’t really advanced as far as it could have is its built-in spell checker. I don’t have a fancy story for this one; the data speaks for itself. Here is a list of words that show up as spelling errors in Firefox 3.6:

Some of the internet’s most popular websites:

  • YouTube
  • Facebook
  • Myspace
  • Flickr

Well-known web technologies:

  • Skype
  • Silverlight
  • Webkit
  • WordPress, CMS
  • PHP, CSS (it gets HTML)

Very common computer words:

  • Inbox
  • USB

Extremely successful desktop software:

  • Photoshop
  • PowerPoint

Apple products:

  • iPod, iPhone, iPad
  • Macbook
  • iMac
  • OSX (it gets Linux and UNIX)

These are all very common words in internet parlance, and it’s ridiculous that they are highlighted as possible spelling errors. Why not add them to the dictionary? A simple white-list that could be crowd-sourced to the community seems right up Firefox’s alley; I wouldn’t be at all surprised to see this addressed in a future release.

What can we learn from this?

My main take-away here is that context is a big factor in software development, and one of the hardest to get right. Even the big guns have room for improvement, which means the rest of us likely do as well.

Categories
Web Misc

Opera vs Reality

2009 was an exciting year for the web browser crowd:

  • Google released Chrome.
  • Apple ported Safari to Windows.
  • Firefox picked up a lot of market share.
  • Microsoft actually produced a half-decent version of Internet Explorer.
  • The iPhone and Android finally made mobile browsing popular.
  • Support for HTML5 and CSS3 was way up across the board.

The term crowd is especially appropriate here because it really is starting to get very crowded. For a long time the browser war has been fought largely between two major players at a time (IE/Netscape, IE/Firefox) and all of a sudden we have four major companies with fantastic browsers available to the vast majority of users. Oh, and then there’s Opera.

Here’s the thing about Opera

Opera is in serious trouble because it doesn’t have a “thing”:

  • Internet Explorer’s thing is its existing market share. It has a lot more users than everyone else, so its going to be a major player for the foreseeable future.
  • Firefox’s thing is its community. Not just its core developers, but the people who create addons or personas or rally everyone they know to go download the latest version on launch day. It’s easily the most passionate user group of the bunch.
  • Chrome’s thing is its brand. When people think web, they think Google. Google has the best search, a fantastic email client, why not a great browser? Users rely on Google for a great online experience, and Google has a lot of high-traffic areas where it can push Chrome.
  • Apple’s thing is its loyalty. Apple fanboys are a loyal bunch — most of them will stick with Safari on their Mac and many will consider getting Safari for any Windows computers they’re forced to use. Apple also has the iPhone, which gives it a growing space where it has the only browser (not that any iPhone users mind — loyalty, remember?).

Opera has nothing. It used to be the most advanced browser for HTML5 support, then everyone else caught up. It used to be a major player in the mobile space, then Apple and Google obliterated it. It used to be a fun browser for geeks to talk about, but now the buzz is all Chrome. It’s not enough to be an alternative to IE anymore; users are demanding more from their browsing experience, and they’re flush with places to find it.

What’s even worse is that there isn’t really anything you or I can do to help. Opera’s engine isn’t open source like Gecko (Firefox) or Webkit (Chrome/Safari) and they don’t have the extensibility of Firefox or Chrome. It doesn’t have the de-facto standard advantage in Windows (IE), OSX (Safari) or linux (Firefox), and even if I wanted to rally some Opera enthusiasts together, where would I start? How many people do you know that have even heard of Opera?

I don’t have anything against Opera (it’s a fine browser), it’s just that it’s no longer relevant — there are too many better options around preventing Opera from picking up new users, and I can’t think of a single significant reason for its existing users to stick with it.

Any Opera fans out there?

Do you use Opera? Do you have any thoughts on Opera’s future? Be sure to leave a comment.