This might seem like more of a graphic design question than a programming question, but I think it has much more technical/programming merit than actual graphic design.

The concept of "responsive" web design revolves around using media queries in CSS3 to detect the size of the viewing device and adjust the CSS rules accordingly - essentially, dynamic CSS. This fills the void on a lot of deployment cases - mobile, in particular.

I think use of media queries is surfacing slowly (I've found that many people don't really know about it), but I'm wondering if there is a reason for slow adoption. Is it impractical for web applications? Is there something I'm missing that might be a fundamental pitfall?

s it because internet speeds are increasing as time goes on and the responsive is no more a real issue, and the effort is not justified anymore?May be I am wrong, because this idea looks cool!
–
Kiran RavindranathanAug 14 '11 at 0:48

3 Answers
3

You have to jump through hoops to get it to actually work. For a site I'm developing I used @media (max-width:800px) to define a stylesheet for phones and other smaller screens. But it wasn't being used by e.g. iPhone.

Turns out that phone browser developers assume that people won't take small screens into account so they lie to the rendering engine (iPhone claims to be more than 900px wide, for example) unless you put in an extra meta-tag to tell it not to lie. When it gets to the point that you're fighting the browser implementers you start to wonder whether it's worth the effort.

I can't speak for everyone, but from my own experience time and money has been the deciding factor. My colleagues and I are always looking at the latest stuff, but designing and implementing different layouts for differently sized devices is a big deal. Especially considering that on my 3 year old nokia 5800 all our websites look fine - bar that I have to scroll to get the sidebar content. We design and implement websites for small companies and self-employed folk.

Well, I think it's definitely difficult to introduce a responsive design to a site that is deployed or mid-cycle, but I think it would be much easier to implement something like this instead of having a whole other mobile subdomain. Luckily though, Rails is abstracting this task a little bit with inherited templates.
–
NicAug 15 '11 at 15:51

Well, I should add that in our case the client actually outsourced the mobile version to a competitor :( I would personally go with templates rather than a different site as well.
–
PelshoffAug 15 '11 at 15:54

But imagine, someone loads a webpage in a windowed browser of a desktop computer. Do you force them to open fullscreen to read everything, or do you accomodate the size to the reduced window and present lots of blank space as they maximize it? You serve the CSS once, at page load!

What about a phone browser that switches landscape/portrait modes as you rotate the phone?
What about a browser that simply has too small resolution and people normally use zoom-in, but you have already adapted to the reported, way too small resolution and the page becomes unreadable?

Just follow the standard guidelines of making a decent universal, scalable CSS and let the browser handle scaling the page to the right resolution.