Timeline for Responsive Web Design vs. User-Agent Sniffing
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 29, 2015 at 9:36 | comment | added | John | What if you are going to serve completely different view for mobile users. What about preventing mobile uses from downloading all the irrelevant data needed for desktop users. User agent is the way to go... | |
| May 24, 2013 at 18:20 | comment | added | Eric King | @Channel72 A 1-column layout lends itself well to any narrow screen width. It hardly matters whether the screen width is narrow because it's a smartphone browser, or a desktop browser in a re-sized window on a giant monitor. Responsive web design attempts to accommodate all scenarios appropriately, regardless of user agent. | |
| May 24, 2013 at 3:57 | comment | added | Mike Gossmann | There's supposed to be, actually. CSS pixels are supposed to be defined using angles and distances not physical pixels. Many manufactures are ignoring this in their default settings though. | |
| May 24, 2013 at 3:51 | comment | added | Channel72 | Well, a 1-column layout usually lends itself well to smartphones. For a tablet, you can get away with a 2 column or even 3 column layout, and for Desktops typically 3 columns works fine. Regardless, the ideal number of columns you display is typically a function of the biological capabilities of the human eye, rather than screen resolution. My point is that it would be nice if there was a tighter correlation between screen resolution and the likelihood that a typical human will be able to easily scan your site visually. At least, CSS3 seems to assume such a correlation. | |
| May 24, 2013 at 3:48 | history | edited | Mike Gossmann | CC BY-SA 3.0 |
Added some more details to the user agent thing.
|
| May 24, 2013 at 3:42 | history | answered | Mike Gossmann | CC BY-SA 3.0 |