Browser Versions
Every couple of months, I have a look at StatCounter’s Global Stats page, it’s probably one of the most balanced internet usage statistics services in the world, as their counter widgets are installed on a wide variety of websites. Most statistics services are based on access to specific servers, like the W3C’s one. I have a great deal of respect for the W3C, but I don’t believe statistics based on users visiting a technical web developer site is balanced.
As a web developer, browser and operating system usage trends are of great importance to me, though often depressing. I feel I need to know what browsers are most relevant for me to test sites against (if only more people did this, the internet would be a better place…). This philosophy has brought up a few questions about geography and intended demographics.
If the site is of a technical nature, should I instead focus on statistics from the W3C site? Should this blog be better optimised for those the W3C suggests? If so, perhaps I should consider Linux fonts and some more obscure browsers.
Does a shopping site primarily designed for European delivery really care what browsers the Asian market are using? In Europe, Internet Explorer 6 had 3.32% of the usage share in September 2010, but in Asia it has 16.26%!
The best solution, of course, is to optimise every site for every browser, but there comes a point where hours (or even days) of extra work would be done for a browser no one will ever use. Time is money, and money comes from the clients. I feel it’s my responsibility to advise clients as best I can to save them money. I guess it comes down to percentages. Do I or my clients care about a browser with 5% usage share? How about 3%? 2%? Where is the line drawn?
The situation is even more complex when you consider your clients needs in more detail. I’ve recently completed a website for a client who owns an iPad and an iPhone – these devices occupy a marginal share of browser use, but in this case special care was needed to ensure the site worked flawlessly on both. On a similar note, though most people begrudge fixing websites for Internet Explorer 6 or 7, if the client is a business that still has either of these browsers installed on their workstations, the fixes and optimisations suddenly become a lot more important.
A lot of my musings on this matter are courtesy of Internet Explorer. I desperately want to drop IE6 from my testing cycle, but I can’t. I kept telling myself “if it’s under 5% share, who cares?”, but such a cavalier attitude doesn’t make clients happy.
I think it boils down to: Write it for Firefox, fix it for Internet Explorer 8, test it in Chrome, Safari and Opera… Then apply whatever fixes are necessary for Internet Explorer 6 and 7 in a separate stylesheet. Lately this approach has been working well – sites work in everything, but don’t have (as a previous client once put it) “Razzle Dazzle” for the lower share browsers.