4 ms·

I'm a web developer, whenever a client asks me about IE6 support, i enthusiastically tell them i'll happily support it. I then show them usage statistics for IE

I'm a web developer, whenever a client asks me about IE6 support, i enthusiastically tell them i'll happily support it. I then show them usage statistics for IE6 and tell them IE6 support costs a flat fee of £10,000 and let them think about it. No client has ever taken very long to decide its not worth it and none have ever taken me up on it, although i'm sure 1 or 2 have asked a different developer to make them an IE6 version, but thats fine with me.

meanJim 15y ago
I agree with this. Although I'm young and naive and I rather not pick up a client (because I have that luxury) that wants IE6 support.
elektronaut 15y ago
I haven't had a request for IE6 support in years, but if I got one I would say something like: "No, I will not do IE6 support for you. You've trusted me to solve your problem in the best and most efficient way, and supporting IE6 would be a waste of your money (and my time)."
- zbuc 15y ago
  Unfortunately, some (very large) corporations still use IE6 across their organizations and require you to support it.
- dasil003 15y ago
  The problem is this is piss poor client relations. When you make a declaration like this you seem arrogant. Effectively you are saying that your knowledge of web development trumps any concerns they may have to the point that you don't even need to know about it. Instead you have to take the time to understand why they are requesting it and then communicate the tradeoffs to them at the appropriate technical level for their expertise.
  - elektronaut 15y ago
    I'm usually less brash and assertive when I'm not making inebriated offhand comments on the internet. Honesty and confidence can go a long way in building trust if backed with demonstrated knowledge, though. In my experience, clients are usually pretty good at providing rationale for their requests, so my implied scenario is a bit of hyperbole. Often when the topic of legacy browsers comes up, it's because the client has been in the process of having a website made before, and is relieved to discover that the technology has moved forward since then.
- idiopathic 15y ago
  Let me tell you about the UK National Health Service. 1 million employees, they are literally saving people's lives every day, and all they are allowed to use is IE6. What your statement shows is not a understanding of how to solve the problem for such a client, but a rather a complete lack of understanding. Check the audience metrics, check the real problem being solved, and leave the grandstanding aside. And for the record, I hate IE (6 or otherwise) and never want to support it. But I am not going let me personal dislike for a technology get in the way of helping a client solve a really important problem.
  - lwat 15y ago
    I'm so glad I've never had a client like that here in Australia. Everyone seems to be OK with the idea of running multiple browsers. We do have clients that use IE6 but we've always managed to convince them to install Chrome or Firefox on their desktops so they can use our software. Some users end up using multiple browsers but that's ok. I guess we're fortunate in the sense that our software is important enough and expensive enough for top management to make IT allow a new browser just for us. At the UK NHS, who exactly is the CIO, who exactly is mandating IE6 and only IE6? Can't that person be reasoned with? Overridden for the good of the NSH? Fired even? Just saying 'oh they're only allowed IE6' is giving up too early.
    - davekinkead 15y ago
      Except certain Australian Federal departments with 70,000+ staff who are stuck on IE6 because their IT boffins only want to use 'secure' web browsers and IT policy doesn't give them any choice in the tools they use.
      - lwat 15y ago
        No see my point is that there is ALWAYS someone above the 'IT boffins' that can force changes in policy like that. You don't fight with the 'IT boffins', you go right to the top. If the CIO or CEO or board of directors decide to use your software, they'll change whatever internal policies they need to make it happen.
notatoad 15y ago
this is the correct way to approach the problem, because it puts the client in control. if you tell them flat out that you don't support IE6, they will see that as a deficiency in you or your agency. you need to let the client feel like they are making the decision to not support IE6.
DrStalker 15y ago
We take a slightly different approach: we offer pricing for both full IE6 support (completely matching the mockup and functionality of other browsers) and doing enough work to make sure IE6 can be used although the styling will not be perfect. Like Tam's approach the key is to give the client options so they can make the call based on their budget and business needs.

meanJim 15y ago

I agree with this. Although I'm young and naive and I rather not pick up a client (because I have that luxury) that wants IE6 support.

elektronaut 15y ago

I haven't had a request for IE6 support in years, but if I got one I would say something like: "No, I will not do IE6 support for you. You've trusted me to solve your problem in the best and most efficient way, and supporting IE6 would be a waste of your money (and my time)."

zbuc 15y ago
Unfortunately, some (very large) corporations still use IE6 across their organizations and require you to support it.
dasil003 15y ago
The problem is this is piss poor client relations. When you make a declaration like this you seem arrogant. Effectively you are saying that your knowledge of web development trumps any concerns they may have to the point that you don't even need to know about it. Instead you have to take the time to understand why they are requesting it and then communicate the tradeoffs to them at the appropriate technical level for their expertise.
- elektronaut 15y ago
  I'm usually less brash and assertive when I'm not making inebriated offhand comments on the internet. Honesty and confidence can go a long way in building trust if backed with demonstrated knowledge, though. In my experience, clients are usually pretty good at providing rationale for their requests, so my implied scenario is a bit of hyperbole. Often when the topic of legacy browsers comes up, it's because the client has been in the process of having a website made before, and is relieved to discover that the technology has moved forward since then.
idiopathic 15y ago
Let me tell you about the UK National Health Service. 1 million employees, they are literally saving people's lives every day, and all they are allowed to use is IE6. What your statement shows is not a understanding of how to solve the problem for such a client, but a rather a complete lack of understanding. Check the audience metrics, check the real problem being solved, and leave the grandstanding aside. And for the record, I hate IE (6 or otherwise) and never want to support it. But I am not going let me personal dislike for a technology get in the way of helping a client solve a really important problem.
- lwat 15y ago
  I'm so glad I've never had a client like that here in Australia. Everyone seems to be OK with the idea of running multiple browsers. We do have clients that use IE6 but we've always managed to convince them to install Chrome or Firefox on their desktops so they can use our software. Some users end up using multiple browsers but that's ok. I guess we're fortunate in the sense that our software is important enough and expensive enough for top management to make IT allow a new browser just for us. At the UK NHS, who exactly is the CIO, who exactly is mandating IE6 and only IE6? Can't that person be reasoned with? Overridden for the good of the NSH? Fired even? Just saying 'oh they're only allowed IE6' is giving up too early.
  - davekinkead 15y ago
    Except certain Australian Federal departments with 70,000+ staff who are stuck on IE6 because their IT boffins only want to use 'secure' web browsers and IT policy doesn't give them any choice in the tools they use.
    - lwat 15y ago
      No see my point is that there is ALWAYS someone above the 'IT boffins' that can force changes in policy like that. You don't fight with the 'IT boffins', you go right to the top. If the CIO or CEO or board of directors decide to use your software, they'll change whatever internal policies they need to make it happen.

notatoad 15y ago

this is the correct way to approach the problem, because it puts the client in control. if you tell them flat out that you don't support IE6, they will see that as a deficiency in you or your agency. you need to let the client feel like they are making the decision to not support IE6.

DrStalker 15y ago

We take a slightly different approach: we offer pricing for both full IE6 support (completely matching the mockup and functionality of other browsers) and doing enough work to make sure IE6 can be used although the styling will not be perfect. Like Tam's approach the key is to give the client options so they can make the call based on their budget and business needs.