Browser Support: The Two Metrics That Count
Post from January 27, 2009 (↻ January 24, 2018), filed under Web Development.
This and many other posts are also available as a pretty, well-behaved e-book: On Web Development.
There are only two things that matter to determine what user agents—or browsers, simple language—to support on any given site: First, how popular is the user agent in question? Second, what’s the “support threshold,” the distribution percentage that makes a user agent mandatory to support?
This might sound completely obvious but it still requires a meiertesque post, as some companies and individuals throw in other variables to the decision what browsers to support. For example, some consider practically unimportant browser Beta versions or rarely relevant operating systems, use unmanageable “grades” or “tiers,” or blindly refer to general concepts like Graceful Degradation and Progressive Enhancement.
Still, the only thing that matters is the browser’s popularity (in your market segment, if you like at least one level of complexity), and your own choice of what percentage makes a browser worth testing for. Supporting browsers is as simple as that; in a corporate environment, a list of browsers to be supported that gets updated each quarter is usually enough.
Since meiertesque posts are not always a 100% clear, here’s what I do every now and then: For an existing site, I’d have a look at its UA stats and compare them with competitors as well as my own heuristics. If the site is new I’d verify my heuristics and assumptions by checking public metrics. Then I’d set a support threshold of about 1% and would make sure that the site works (looks and behaves about the same, that is) in all browsers that are used by at least this 1% of visitors. Graceful Degradation and Progressive Enhancement would be instruments to be used, but they aren’t per se important to decide what browsers to support.
About the Author
Jens Oliver Meiert is a technical lead and author (sum.cumo, W3C, O’Reilly). He loves trying things, including in the realms of philosophy, art, and adventure. Here on meiert.com he shares and generalizes and exaggerates some of his thoughts and experiences.
If you have any thoughts or questions (or recommendations) about what he writes, leave a comment or a message.
On January 27, 2009, 21:43 CET, Dave said:
I don’t think there’s such a thing as “mandatory to support”. The key measure is the return on investment, which means there’s definitely another factor: resources required to support a user agent. If I can make the site work in Browser A in 10 minutes, but it will take all day to make it work in Browser B…
If you want to get fancy, you could start talking about the return you get from users of different browsers. If you’re selling something shady and you know you won’t be able to trick 99% of Chrome users into making a purchase, then why bother supporting Chrome?
Shouldn’t we create websites with people in mind, not browsers?
I for my part, have decided to throw out all my IE hacks (on all my web sites) this year…forcing people to switch to newer Versions of their Browser-Software. So far it’s working.
The usage of IE alternatives went up 12%, traffic is steady. 😊 Like Dave said,..there is no such thing as “mandatory support”!
On January 28, 2009, 21:56 CET, Lauren said:
I have actually seen quite a few people hit the moto of forcing the switch on users. However, when you are dealing a money site (which you may be) the last thing you want to do is make your users feel forced to do anything. Jens approach is rather safe and even going beyond to support that other bowser is worth it. I would rather take an extra day to bring in more visitors and potential customers. Support as much as needed without trying to decide for them. These are typically the people who are comfortable with the 800×600 resolutions : /
however I would like to see firefox take over - or something other than IE
It is sort of implied in the post but it is worth mentioning that in the case of intranet websites it is often possible to restrict support to the only browser that is authorised for use by the owners of the intranet (possibly more than one version).
On May 19, 2010, 8:29 CEST, Cassey said:
As explained in the post, it is worth mentioning that in the case of intranet websites it is often likely to restrict support to the only browser that is authorized for use by the owners of the intranet. The other point is if you’re selling something dappled and you very well know you can’t trick 99% of Chrome users to purchase, then why we need to bother about supporting chrome.
On January 25, 2011, 16:55 CET, Mike said:
I agree, it would depend on the popularity of your visitors browser. Anyways, browsers will update their to adapt new sets of codes.