Posts Tagged ‘browser’

Google Chrome, changing browsers and changing behaviours

Thursday, July 14th, 2011

Due to a bug in Firefox 4 I recently moved my default browser over to Google Chrome and I have been really impressed. Chrome does everything just a bit better; it is a bit faster, a bit easy to use, a bit cleaner with the interface, all of these add up to a big overall improvement. The main point for me is that Chrome does the basic things well i.e. browsing, searching, bookmarks and downloads. For most people this is all they will use the browser for.

Like most people I do not change browsers that often so it takes an external event (such as a bug or operating system incompatibility) to get me out of my comfort zone, it was the same when I moved from PC to Mac, my PC kept crashing so it gave me real incentive to change.

This made me ask myself the question how can a company incentivise people to change their default behaviours when there will be a time investment on the consumers part?

  • Make the change simple – Chrome allowed me to import all of my bookmarks and preferences very easily
  • Intuitive design – don’t make people invest time in learning new functions use industry standards
  • Configuration – make sure you can tailor the product to get the best of both worlds e.g. Chrome allowed me to add the bookmarks bar just like Firefox did
  • Constant improvement – keeping adding new features and updates so that there is no reason to move back to your old provider
I am sure there are many more but these are the ones from the top of my head.

 

Graded Browser Support – Who Cares About IE6

Friday, February 27th, 2009

One of my pet hates is browser rendering, and the fact that different browsers all display differently.

We spend an awful lot of time and effort trying to get content to render the same on Firefox, Internet Explorer, Safari, Chrome etc and the list seems to be growing. Most of the phone calls from clients are about how their site renders in IE5.5 on a 200 year old PC! This applies to large corporates as well, most of the big organisations we work with are still using Internet Explorer 6.0, which was released in 2001!

Pixel perfect design is simply not achievable any more and spending a larger percentage of the development budget trying to achieve it seems like wasted money to me.

So I have decided to adopt a policy of graded browser support, the essence of this is:

Browser support should focus on usability and accessibility rather than pixel perfect design. Sites should render in all browsers, but provide advanced features and aesthetics to those which can support it.

Basically your focus should be on does the site work (functionality) as opposed to pixel perfect design.

This is not a new concept, some organisations such as the BBC and Yahoo have been using this approach for some time. Even the UK government has changed their guidance on this matter (paragraph 39):

You should check that the content, functionality and display all work as intended. There may be minor differences in the way that the website is displayed. The intent is not that it should be pixel perfect across browsers, but that a user of a particular browser does not notice anything appears wrong.

Links of interest:

BBC browser support
Yahoo
UK Government guidance on browser testing