Responsive Design, the ugly
It seems lately that everyone is talking about responsive design and few people are actually trying to implement it. After much research, a few attempts, and some heated, yet passionate, discussions I have come to the conclusion that some of it should never leave your local host. Don't get me wrong, I love pushing the limits, but I also think it is important to keep the end user in mind.
When I was younger, I always wondered why large websites were so shitty. I promised myself that if I got the opportunity to redesign a huge site, it would be the latest and greatest thing. My first crack at this was working at MLB.com. Now granted it was not a redesign, but I did fight for what I believed in. Because of that I was one of the first front-end developers to introduce HTML5/CSS3 to the site.
I now work for M. Shanken Communications where I have many opportunities to help lead the digital front. I work for an awesome boss and have an amazing team. We are all on the same level and we want to create the best products that we can. Now is my chance, now I can make a difference, now I can uphold the promised I made to the younger me. I think somewhere along the line, my ideas of what was the "latest and greatest thing" for our users was crossed with what was the "latest and greatest thing" in front-end development.
Mobile first is the thought that you design for the simplest browser first, which in many cases is mobile. For the most part this makes a lot sense. For older phones that don't support media quires, they will be shown the mobile version by default. As you know IE doesn't support MQ either, but that's ok we have respond.js to make it understand.
Now let toss in a fact to further our reason on why we should use mobile first. According to Marry Meeker "Within the next five years, more users will connect to the Internet over mobile devices than desktop PCs." That's great, except as of now that is five years away. A lot has changed in the past five years, shit even in the past five months a lot changed. But what about the users of 2012?
Percentage Based Layouts
I can no longer accept that percentage based layout are realistic for large websites. The main reason for this is pixels and percentages don't mix. I don't want to go too off topic, but one of the main ways websites make money is off advertising. How does a 300x250 pixel banner work into percentages? It doesn't look at Boston Globe. They cut off a part of the ad. I wonder how the advertisers feel about this, or even if they are aware of it.
Yeah, I know there is some simple math you can do to convert a pixel width into a percentage based width, but it doesn't solve much. Let's be honest the only people that grab the corner of their browser and drag to resize is us, developers.
There is also the problem that some browsers take your beautiful math and round it. Funny thing is that we are not pointing fingers at IE, this time, Chrome and Opera are to blame this time. Steffan Williams has a great article that shows how each browser behaves in a percentage based grid. Another thing is percentage based layout is nothing new, also these browser issues are old too. John Resig wrote about it back in 2008 Sub-Pixel Problems in CSS.
The Bottom Line
Let's keep graceful degradation in mind and always build the best possible version we can. I know this rant seemed to trash responsive design, but there is a lot of great things out there right now that are enhancements. Take a look at what Chris Coyier and Paravel have accomplished for flexible videos with FitVid. There are much more amazing things out there that I am currently testing and using on our projects.
I think it is great to experiment and try all these techniques out. I also think you need to be aware of your surroundings. I am very excited to see what tomorrow will bring, but you have to be realistic of what today has to offer.
Users can be a pain in our ass, but I love them all equally. It is up to all of us to provide a usable site first. Part of our job is education, if we want to push the limits with all that HMTL5/CSS3 has to offer, we need to inform them on what the latest browsers have to offer.
At the end of the day, the users comes first.