dingloo - 4:07 pm on Mar 26, 2010 (gmt 0)
As we develop websites for many clients, during the requirements gathering process itself, we try to find out the client's interests in:
1. Machines: (MAC, PC, Ubuntu, etc)
2. Browsers and Versions (IE 5.5, IE 6.0, IE7, IE8, FF3, FF3.5, etc)
3. Screen Resolutions (800 by 600, 1024 by 768, 1600 by 1200, etc)
We also get the client's primary choice browser and develop the application to work on that browser only - we call it 'Single Browser Functionality'. Our QA team approves this and as soon as it is done, we give it to the client to check it on this browser.
While the client tests it on that browser, our QA team now tests the application for 'Cross Browser Functionality', which also includes various resolutions, etc.
This process helps us to make sure the right expectations are set and delivered accordingly. This also helps us in our pricing accordingly.
We also believe this model will help us scale to mobile devices (iPhone, WAP, etc) based on the client's choice.
Sorry if this post was not exactly on the topic (which was only about cross browsers), but felt it would help any one who is unsure about how to handle clients who might come one day and say 'Hey why does the site not work on this browser', etc.