Non responsive
It’s true. If you see a new site released you, as a web developer, grab the side of the browser and start dragging. If it doesn’t respond you scoff and move on.
In this case James Young goes through the reasons (like Go Cardless have done) why responsive wasn’t the answer in this case and puts down some damn fine reasons why.
Listen to Twitter and you’ll believe that building anything less than mobile first, fully responsive websites in this day and age is very very wrong. It’s not always that simple.
My two current projects at work aren’t fully responsive or device agnostic and when I look at all the things I’ve written about over the last year or two, they’re at odds with a lot of what I’ve supported and tried to champion in my work but to be honest it’s nice to concentrate on some known variables for a while.
An excerpt from Non responsive
