18

A year ago a big company asks us to create 'A fully dynamic web-page' for their products because they 'want to have the ability to change all the content' by themselves. They also wanted the design to be mobile first without giving too much effort for the desktop/laptop layouts, because ~85% of their traffic comes from mobile devices.

It has been a year now that this website is up and running.

It has been a year they are complaining that the website does not 'properly show' in Internet Explorer.

It has been a long dreadful fucking year that their useless mucus-brained brand manager is sending me a pile of scrambled folders, filled with numerous over-sized images, and content written in a dozen of difference Slavic languages which i don't understand; asking me to change/update the content for them on their 'FULLY DYNAMICAL RASPONCHIVE MODILE FIRST INTRRENOT WEBPAPER'

Pubes, spit and boogers and your daily food bitch!

Comments
  • 3
    Lol, good rant.

    But honestly, I can't understand why all web devs think it's ok to not support IE11?! It is still around and especially larger companies must support this shitty thing.
  • 7
    @sboesch nobody 'must' do anything

    At my job we say fuck it and show a warning label
  • 2
    @alexbrooklyn of course you 'must' not, but you should if you want to deliver your client a good product. Delivering a website which doesn't run properly in IE 11 is like delivering a car which can't drive on snow. It's still a car, sure, but not as good as others.
  • 6
    @sboesch I wholeheartedly disagree, but let's keep it at that
  • 0
    @drac94 sure, as if you would even notice if a website runs on IE11 if you're not even supporting it ;)
    In about 99% of the cases I don't even write any hacks to support it. Postprocessors do everything by themselves, without any effort (assuming the code isn't trash already).

    Usually we also don't care for IE11 by default (except having a toolchain which does out of the box). But we analyze the clients target audience and make them aware of the IE problem, so they can decide if it's worth the effort.

    I don't criticize modern-only websites (well, I did...), I only wanted to criticize "bad" consulting. Saying "we don't support IE, nobody needs it", while the client obviously needs it, is not a good approach IMHO.
  • 7
    @sboesch I use the 3% rule.

    If a browser is responsible for less then 3% of annual sales (ecommerce), I don't go out of my way to support it.

    Chrome: 40%
    Safari: 20%
    Firefox: 19%
    Edge: 14%
    IE11: 2.4%
    IE10: 1.5%

    Nintendo Switch: I had 5 purchases, should I go and buy a switch and make sure it works for this guy too?

    We have to draw a line in the sand somewhere.

    Now In saying that, I will check that the happy paths for login, browsing and checkout are fully functional for "unsupported" browsers but beyond that, I'm not to worried if an image sits out of place or some animation doesn't load correctly, the user can still get through the key areas without to much hassle.
  • 2
    @C0D4 I totally agree. But if a "big company" (eg Amazon) makes only 1% of sales with IE users, it still would be millions in comparison to the few bucks it costs to provide a good UX.

    Of course it doesn't make sense for a small shop, but I still like to stay transparent and let the client decide, instead of delivering them a website below their expectations. I'm not doing it for free of course.
  • 2
    @sboesch 3% for my sites is about 1-2mil per year.

    Yea it's a significant drop in the barrel, not amazon's barrel.

    Which is why I maintain a level of usability.
  • 1
    There is another take on the whole 'website as a car' thing

    Delivering a website which doesn't run properly in IE 11 is like delivering a car which does not use coal and souls of children as fuel. Its still a car but its better than the others that do.

    Another funny take is the following:

    1) First we were seriously troubled by one particular disease and complained about it (IE)
    2) Then the time came that we learned that there is no reason to worry about this disease because there are multiple cures (modern browsers, Microsoft dropped support, avoiding usage)
    3) But then we are like 'Oh No! We must keep supporting this disease!'

    Let this old piece of software die.

    Those who still use it willingly, they must evolve and adapt sooner or later.

    Say you got a headache. What are you gonna do? Pray to the old mountain Juju as you perform the sacred dance of go-away-pain to cure your headache? Or are you going to take a painkiller?
Add Comment