Re:A different way of looking at responsive design: Intentio...
by cheald on Tuesday August 27, 2013 @02:31PM
(#6285247)
1) User agents lie. Frequently.
2) A user agent doesn't encode any information about the actual metrics of the device.
Doing layout by user agent is basically a worst-case hellhole of browser-specific codebase fragmentation. There's a very good reason why best practices have been trending away from "test for vendor class" and towards "test for agent capabilities".
Re:A different way of looking at responsive design: Intentio...
by benatkin on Tuesday August 27, 2013 @08:07PM
(#6287194)
Well a sufficiently complex framework could deal with it, by making another trip to the server if it discovers the code being sent down the first time isn't good enough.
Re:A different way of looking at responsive design: Intentio...
by untog on Tuesday August 27, 2013 @02:49PM
(#6285355)
It sends the User-Agent, which can be used to determine whether it's the desktop or not.
What is "desktop"? An MS Surface Pro would report as a desktop browser, but it's a touch interface. You can also resize the browser window- what then?
So some client-side responsive design would still need to be used.
Which is the point. The server can't know conclusively so why make it try?
Re:A different way of looking at responsive design: Intentio...
by martin-adams on Tuesday August 27, 2013 @02:38PM
(#6285283)
The fact that I'm on a desktop does not take into account that my browser window may be smaller than my 'desktop screen'. Responsive is the way to go because it works.
Re:A different way of looking at responsive design: Intentio...
by nostrademons on Tuesday August 27, 2013 @03:12PM
(#6285492)
CSS3 media queries can often fulfill the missing link for screen sizes, aspect ratios, etc.
I think a hybrid approach would be too tedious for someone developing a website to do, in order to get the payoff of sending less to mobile browsers, but it may be worth implementing in a framework.