A few weeks back I attended the SASS meetup ran by the awesome Claudina. The topic for the night was SASS and how it can be use to implement Responsive Web Design. The presentation was very good and it got me thinking about the topic of RWD again. Now if you have been following my blog, you would know that I’m not a fan of Responsive Web Design, and nothing have changed, if anything, my resolve has only strenghtened.
The presenter stated anecdotally that Ethan Marcotte, the face of RWD, was 50/50 on it’s future. That even he has reservations about RWD is telling, now allow me present yet another argument against RWD.
In my work I go back and forth designing the same product for various platforms (iPhone/Android, then desktop website, then iPad, then mobile web, rinse and repeat.) It’s a linear process, where I solve for one platform before moving onto the next. And with each new platform, I make changes based on the lesson learned from the one before. Sometimes the changes are radical. So it’s not about deploying one product across multiple platforms that you have with RWD, but many iterations of the product.
By the time I get to the mobile web, the product would be much evolved from the iPhone design where I started. It’s an incredibly valuable process of evolution that you get from designing for individual platforms that would missing from any Responsive Web Design project.