> Now, we're to be expected to make these same sites, using the same general design, > work on devices with ittybitty screens and radically different physical

> Now, we're to be expected to make these same sites, using the same general design, > work on devices with ittybitty screens and radically different physical interfaces? No, we are not expected that. However you can have the same theme for your desktop, tablet, mobile version and the same content. > You'll have your blog or what-have-you, and your blog will have a mobile version, > and a desktop version, and they will be completely and totally 100% separated from > and independent of each-other. Oh no. This failed miserably with "accessible versions" of sites before. In most cases the moment you start to separate your content you already blew it. We already have tools to separate content and markup from design. We have CSS media queries. There are some problems (e.g. images), but otherwise we can already make it work. Google for responsive web design, adaptive web design: there is something to learn. > I think the "right" way to do this is to continue to make the desktop version of a site > the default Take a look: http://www.lukew.com/ff/entry.asp?933 http://www.lukew.com/ff/entry.asp?933 > and then check the user-agent of the request on the server Sometimes useful, bet generally a bad idea. > Let the server handle which layout to serve up, not Javascript That's CSS job, not Javascript's: http://www.alistapart.com/articles/responsive-web-design/ http://www.alistapart.com/articles/responsive-web-design/