Print this page
Tuesday, 29 December 2009 08:11

Browser Coup d'état

I recently came across this cause, Browser Coup d'état being promoted by .Net Magazine. The case presented is well articulated and illustrate a point that many of my clients might not otherwise understand.

I would like to take the argument one step further though. While we, as web designers, should stop developing for this dinosaur of a browser, it seems to me that the future is being overlooked by some web designers, and certainly by most of our clients. Mobile device browsers are the future of web content. Is it the designer's responsibility to develop for the browser? OR the browser's responsibility to render web standard code?

Related items