The problem of responsive images as part of an overall responsive web design is a tricky one. Something I had to wrestle with in a recent project, with not entirely satisfactory results. Jason Grigsby’s “part 1” article introducing the issues is a great place to start if you’re thinking seriously about this (and you should be if you are doing any responsive design).
Update: Almost immediately, here’s Jason’s “part 2” article on the current range of solutions (both good and not so good) to the responsive image problem.
Luke Wroblewski’s Data Monday for this week focuses on the usage of mobile-optimised websites versus equivalent native mobile apps.
I’ve just been having a quick look round the newly unveiled Boston Globe website. It’s a responsive design. Responsive in the sense that the page reconfigures itself depending on the type of device it is being viewed on. It’s an approach close to my heart as I’ve been working on a similarly enabled website for the past 6 months. The one thing that has consistently struck me is the feeling of capability you get from a responsive site. Fixed-width sites seem clunky and ancient by comparison.
Don’t hold back, just push things forward from Ithaca Audio on Vimeo.
Featuring Shaft, Star Wars and the BBC World Snooker Championships.
I love this interactive demonstration of how focal length, aperture size and other factors affect a camera’s depth of field. A real “ah-ha!” moment.
Two most interesting points in this presentation by Jeffrey Zeldman.
- Understanding (if not writing) HTML and its semantic structures and rules is a fundamental, non-negotiable skill that all web designers need to have.
- Responsive Design is a tool to enable a small-screen strategy, but a mobile strategy (which should incorporate consideration of screen size and content display) is something larger and more complex.