I actually agree with the point that I don’t consider images to be an issue at all in responsive design. I’ve never had a site so full of “large” images that had to be scaled down, that there was a huge hit in performance, and I’ve done some pretty large sites. Most of the images don’t get scaled down very much anyways, so the savings in performance is negligible. I’ve also yet to see a huge difference in quality between retina made images and not for the web – I mentioned this in my HandHeld conference talk, but it comes down to priorities. Is it worth all that extra time and code to make a million versions of your images? Is it worth downloading a double-sized image for retina? If it’s not pertinent to the site, I don’t waste the time or bandwidth.
Amber Weinberg
I actually agree with the point that I don’t consider images to be an issue at all in responsive design. I’ve never had a site so full of “large” images that had to be scaled down, that there was a huge hit in performance, and I’ve done some pretty large sites. Most of the images don’t get scaled down very much anyways, so the savings in performance is negligible. I’ve also yet to see a huge difference in quality between retina made images and not for the web – I mentioned this in my HandHeld conference talk, but it comes down to priorities. Is it worth all that extra time and code to make a million versions of your images? Is it worth downloading a double-sized image for retina? If it’s not pertinent to the site, I don’t waste the time or bandwidth.