BY: Keith Essary
In a move no doubt indicative of more to come, Facebook has announced that it will no longer support Microsoft Internet Explorer Version 6 (IE6) for some social networking features. Google / Youtube killed support for the IE6 web browser earlier this year.
Web Browser compatibility is one of the most common conversations had during the development of a website. In web dev, one size certainly does not fit all. It is often a tedious process to develop for each and every web browser. In fact, this goes much further than developing for every brand of browser into the different versions and platforms of each one. For example, consider Microsoft Internet Explorer 6, 7, and 8, Firefox 2, 3, 3.5, and 3.6 for Mac and for Windows, Safari 2, 3, and 4 on Mac and on Windows, Chrome for Mac and Windows, etc. If the site requires a mobile version (most do) then you also have to program and test for Safari on the iPhone and iPad, Opera Mobile, the Blackberry browser and on and on.
This can be achieved in a couple of primary ways:
- The most common method is to “dumb down” the code. This means make the development simple enough that all browsers can render the code appropriately. You might call it the lowest common denominator method.
- The more time consuming method (and consequently, the more costly method) is to detect which browser the visitor is using and serve them a website version appropriate for their respective browser (some versions can be used for multiple browsers). This allows for more advanced features to be shown to those who have a supporting browser and a limited version for those who do not. This method must be used when you are developing a mobile version.
All self-respecting web development companies are monitoring web browser usage statistics. And the determination of which browsers to support should be development specific based on the scope, purpose, and budget of the development.
There are some browsers and browser versions that simply must be included in all developments for public use. However, older and obscure browsers should always be in question for cost savings or feature impacts to the project. Using IE6 as an example, providing support for a browser used by 4.7% of visitors can cause the development features to be limited for the other 95.3% or create costs comparable to performing a separate development project. That being said, 4.7% still represents a lot of visitors.
A decision not to support a particular browser is often a hard one as no one wants to exclude any potential visitor. However, sometimes this is just the nature of the technology beast. In all cases, decisions of which browsers to be supported should be decided at the onset of the development, redevelopment, or feature addition.