anyone that claims "responsive design" as a best practice clearly has never actually tried to support multiple contexts or devices.
2:41pm Mar 22nd 2011 via Tweetie for Mac
creating great contextual experiences has absolutely nothing to do with markup or css.
2:45pm Mar 22nd 2011 via Tweetie for Mac
@fling As someone working on a sizable responsive redesign, those strike me as fairly broad strokes, Brian. Care to go into more detail?
2:47pm Mar 22nd 2011 via Twitterrific for Mac in reply to fling
responsive design seems like the easy hack that attempts to avoid solving the much harder but more thoughtful solution
2:49pm Mar 22nd 2011 via Tweetie for Mac
@beep @fling Me, I think responsive design is important tool, but often: mobile apps/sites need mobile content, not just rejiggered layout.
2:51pm Mar 22nd 2011 via Twitter Web Client in reply to beep
@fling Agreed, but sometimes a necessary hack. Useful transitional step when people are trapped, eg, by their CMS into single HTML page.
2:53pm Mar 22nd 2011 via Twitter Web Client in reply to fling
@beep underlying components and content will also often need to change - responsive design by itself isn't enough. /cc @fling
2:53pm Mar 22nd 2011 via Twitterrific in reply to beep
@fling it has it's place, but it's by no means the final solution. 100% agree that the rest of the process is *much* harder. /cc @beep
2:55pm Mar 22nd 2011 via Twitterrific in reply to fling
@bryanrieger Still, there’s more overlap than these “mobile web vs. responsive design” discussions imply. Not a fan of absolutes, me.
3:00pm Mar 22nd 2011 via Twitterrific for Mac in reply to bryanrieger
btw, we had this debate five years ago and "responsive design" didn't win... but of course only a few were paying attention.
3:04pm Mar 22nd 2011 via Tweetie for Mac
@fling five years ago media queries were entirely academic.
3:06pm Mar 22nd 2011 via Twitterrific in reply to fling
@fling I used to agree w/ you, but I now recognize @beep, @scottjehl, and Riegers, I realize they aren't shying away from tougher problems.
3:14pm Mar 22nd 2011 via TweetDeck in reply to fling
Jason Grigsby, ☁4
@fling people start working on how to do RWD mobile first. can they pull it off? my guess is yes. Is it best in every case? no.
3:26pm Mar 22nd 2011 via TweetDeck in reply to fling
The struggle will be getting beyond merly "regifting" the desktop Internet experience for mobile. / cc @fling @beep
4:34pm Mar 22nd 2011 via Twitter for iPad
After all wew have two other screens, tablets and tv, with vastly different contexts we to consider. //@fling @beep
4:36pm Mar 22nd 2011 via Twitter for iPad
@ktamura I honestly don't get the confusion. RWD isn't design for mobile. It's adaptive layout design. That's it. No? /cc @fling @beep
4:47pm Mar 22nd 2011 via Twitter for Mac in reply to ktamura
@ktamura It's making sure your layout doesn't look crap on diff. sized screens. Nothing more. Or am I missing something? /cc @fling @beep
4:48pm Mar 22nd 2011 via Twitter for Mac in reply to ktamura
@markboulton 100% agree with "RWD isn't design for mobile. It's adaptive layout design." Put that on a billboard. /cc @ktamura @fling @beep
4:51pm Mar 22nd 2011 via Twitter Web Client in reply to markboulton
@markboulton a lot of the debate goes back to the "one web" vs "mobile web". RWD has become the straw man for one web. //@fling @beep
4:52pm Mar 22nd 2011 via Twitter for iPad in reply to markboulton
@markboulton RWD assumes that media queries will correctly adapt content to browsers. which it doesn't //@beep @ktamura @StuRobson @colly
4:59pm Mar 22nd 2011 via Tweetie for Mac in reply to markboulton
@fling Okay, perhaps I misunderstood what you meant by “adapt content.” My early RWD examples are focused on layout, not content.
5:09pm Mar 22nd 2011 via Twitterrific for Mac in reply to fling
@beep sorry, you are absolutely right. I think I conflated the two.
5:21pm Mar 22nd 2011 via Tweetie for Mac in reply to beep
Connect with Twitter
A website by @jwheare