The Eric Wroolie Blog

So, Internet Explorer is in big trouble.  Both the France and Germany governments have called for web users to find an alternative browser this week this week.  Most tech-savvy users have already moved to Firefox and Chrome (I’m now completely using Chrome), but the majority of surfers still use the default IE.

Even more interesting, most corporate environments I’ve worked in support only Internet Explorer internally.  You are simply not allowed to install another browser.  I’ve worked on projects where the intranet application we are developing only works with Internet Explorer—usually because of bad coding/testing—but no one will fix this because “we only support Internet Explorer”.

I remember one high-level manager in an investment bank tell me—“Seriously, Eric, I can’t see us ever moving away from Internet Explorer.”

The lack of cross-browser support in the ASP.net developer community has been a big pet-peeve with me for years.  You don’t find this with PHP, Java, or Ruby guys.  But Microsoft developers stick with Microsoft browsers. 

I’ve had the arguments so many times in various contracts—“We should support Firefox too.  It only takes a few minutes to test functionality if we do it early enough, but will be a huge task to implement it later.”  I can remember having this argument a half-dozen times, at least.

It has never been easier to do cross-browser development (you should have tried it in the Netscape 3/IE 3 days—that was painful), but it still gets overlooked.

Even the online banking site for my  business bank account only renders properly in Internet Explorer.  This is a huge pain to go through all the necessary security logins for banking—only to realise you are in the wrong browser and you can’t read the page.  I’ve nearly changed banks because of this frustration.

An ideal web development team would have different developers using different browsers.  In a team of 4 people for example, have one person on each of the 4 major browsers—IE, FIrefox, Chrome and Safari.  Better yet, adhere to proper XHTML or HTML syntax (most of the time, apps only support IE because of some malformed html that Explorer allows). 

But for years I’ve heard the same argument from different people–“We don’t have that kind of time”, “It’s an internal application and the we only support Explorer”, and “We’re not a software house.  But now, when governments are recommending that we switch browsers, these developers haven’t even given their users this option.

This could kill Internet Explorer or at least severely weaken it.  I see a lot of “Make this website work in Firefox” projects coming up.

The best book I’ve read on website usability is “Don’t Make Me Think” by Steve Krug.  It’s pretty much considered the bible of web usability out there.  A very talented developer introduced me to it years ago and since then I’ve sent it to some of my clients.

I found the following video on the fantastic Signal vs Noise blog from 37 Signals.  It’s a one hour introduction to web usability given by Krug in 2008.  If you have a bit of time (I know an hour is a bit long), it really is an interesting talk so have watch.

The url for the video is (on Signal Vs Noise) is http://37signals.com/svn/posts/2092-i-cant-think-of-a-better-intro-to-the-essential