Discussion in 'Website Design Forum:' started by glenwheeler, Oct 11, 2010.
So, this came up in conversation today. If a client wants IE6 support should we be charging extra?
You should charge appropriately.
If IE6 will take you an extra week of bug fixes, then charge them a week's extra at whatever rate (or factor it into the final cost, if not done on a daily-rate basis).
If IE6 won't cause you a ****-tonne of problems then don't whack 10% onto the price, that's just being a dick.
it's not fair to put a tax on your client for doing something you might not enjoy doing.
Charging appropriately and accordingly is the only option if you're running a moral and ethical set-up, surely?
Well TBH how we do it is we will code in the majority of browsers, IE 7,8 Firefox and now Chrome is over 10% Chrome. Safari, which tends not to be an issue as we now code for Chrome, Opera and IE6 are classed as minority browsers and as a result it's Â£45/hour to code for it.
What you find is TBH people tend not to care or if they do we make even more of a profit for the trouble. Either way for our workload and since I have taken on my job I have learnt how much people will pay for simple things and that its not worth adding an hour on to your development time for the same price.
End of the day, especially with IE6 if more people did this more people would use more advanced browsers and Opera would get round to fixing their bugs, but our clients don't care TBH 90% of our business, if we don't turn it away, tends to be repeat proving that.
Typically, if IE6 support is requested then its factored in on my initial costings, if its an additional request mid to end of project then its charged at my hourly rate.
Much like taking a car to a garage to have your engine oil changed, if you then want to add changing the gearbox oil, you just get charged for the additional time and labour at the going rate.
I also factor IE6 in my initial quotes, as its always an extra few hours work no matter which way you look at it..
Cost your project with good ie6 support included, but offer the client a discount for passing up full ie6 support. This way you are not hitting them with an extra charge, but offering the option of a discount instead - turn a negative into a positive.
Also, it's not as clear cut as ie6 being supported not not - agree on the level of ie6 support: full rendering fidelity being the most expensive and time consuming option, while just making sure the site works in ie6 (but may not look fully as intended) is more realistic.
Jumping through flaming hoops to make an elaborate design look just as intended in ie6 is a waste of time and money and can compromise your markup which is bad for performance, accessibility, mobile support and standards compliance. It's not so easy to explain this to clients, but offering a financial incentive can help.
You have got to ask yourself what type of client still uses IE6 and is their business worth the hassle?
I think it's more that their potential clients may still be using IE6, a lot of big companies are still running IE6 due to lack of time/funds to upgrade them all.
I work at a University, over 20% of our site views are still on IE6, we can't ignore it, no which way you set it.
If we outsource any development work, those who take it on HAVE to give ie6 support.
Like greg said, it's not your clients using it, it's their users
I would say that the majoirty of users of IE6 are instituions but I would also say thats beggining to change in a big way. A couple of our big clients are now running IE8 accross all their systems.
And as far as I know since we've stopped supporting it, before my time with the company, but we haven't had one client come back even asking us how much to code for it yet alone asking us to support it and we give them all browser useage data for thier own site(s), and loads of other details most will know what I mean.
I honestly think that now 8's out and 9 on the horozion, and that all new windows machines come with IE8 that a lot of the big companies are starting to take the plunge and say maybe nows the time, especally as more and more people are dropping support for it and thus they need to upgrade to keep on top of productivity. Where as before support was still widespread so producity wasn't effected.
Separate names with a comma.