Tag Archives: marketshares

Browser compatibility: Look at your market!

8Today I want to talk about a topic a bit touchy, the web browser backward compatibility. And in particular a strange behaviour: “The worldwide market share analysis followers”.

This is for me the biggest mistake in the web development when trying to figure out what to do and setup a backward compatibility plan. For the purpose of this article, I’ll take a case I personally had to face today. I’ve quickly developed with Bootstrap.js and JQuery a beautiful and reactive CV web site. It took me about 5 hours max, deployment to the Microsoft Azure cloud included. But before going live I would like to test it against different browsers to be sure about the displays. It’s okay for the Chromes, Firefox’s too, on my android tablet with integrated browser and chrome browser too, on my android samsung mobile too and then, the horror ! It totally sucks with IE 8 and lower… well… Let’s take a look at the famous “worldwide browser market shares” to figure out the impact of that. I use one of the reference analytics website, allowing me to export datas as csv and play a bit with Excel. The complete spreadsheet book is available for download at the end of this article. Here’s the world wide top 20 browsers in terms of market shares:

WWShares

Okay but who’s compatible? I’ve aggregated these market shares based on the compatibility and assuming that the ‘other’ part wasn’t compatible to face the worst case:

WWCompatible

Damn, 20%… I’ll need to take that in account… that’s pretty huge… So I’ll need to dev… STOP ! Who am I really targeting with my CV website? Well, future client and recruiters, mainly in Belgium… So let’s refine the results and take a look at the Belgian situation instead, perhaps it’s better:

BEShares BECompatible

Only 10% remaining… And now let’s refine again the analysis by testing the “others” in terms of compatibility :

BECompatibleOthers

Only 6% of possible incompatibility in the worst case… Well… That’s acceptable for me. The site will work fine in terms of content, just some features will be a bit ugly and the user experience will perhaps suck a bit, but anyway, most of the viewers will have great experience on it.

So will I spent the same amount of development time to the backward compatibility feature? Well, perhaps in the future, but it’s really not a priority.  If my target was the entire world, then yes I should, but let’s be honest, I don’t really care about Chinese or Russian recruiters. So what’s the point of these graphs excepted playing with Excel ?With this I really want to demonstrate you two things:

First, when you have to be backward compatible, don’t do it because you have to and everyone say it’s great to be, but because you have to. This point lead me to the second, always define and keep in mind your audience and don’t work based on “global datas” or techies chatting. That’s true for web development but also desktop applications, trainings, writing, everything! It sound obvious, but once again let’s be honest, who had never spend too much time on features or improvements who appears to be useless or minor once in production?

To conclude, keep that in mind: Know your target and it’s always better to develop for the future than develop for the past !

Catch you next time and keep it bug free !

You can download the Excel doc here