Developers foresee ‘Retina War’

1x design could be 'taxed' or dismissed as an annoyance

Developers foresee ‘Retina War’
Apple's new kit could see designers prematurely abandoning 1x design

Designer Wells Riley has in a blog post claimed that a 'Retina War' is now upon the web design community, sparked by iOS devices and other smartphones with high-res screens, and further exacerbated by the new MacBook Pro. Riley said many websites and apps will "make the leap to hybrid Retina + 1x sooner [rather] than later", and he asked how long it will be before designers abandon 1x.

Riley noted historical precedent, with designers dumping older versions of IE despite the Microsoft browser still having a large market share, or imposing a development 'tax'. He asked: "How long before designers start imposing a '1x tax' on consumers with non-Retina computers because it's too expensive and laborious to maintain two separate asset libraries?" Riley also stated that it's effectively impossible to design with 1x on a new MacBook Pro, that existing software doesn't help, and that few strong solutions are available for web designers to rapidly rework images between 1x and 2x.

Opera developer relations manager Chris Mills said he could see Riley's Retina War as a possibility "from certain camps", despite high-res displays probably not becoming the norm for years. "It is the same kind of stupid argument as 'only designing for WebKit', or 'only designing for IE4 or Netscape 4' many years before that," he added, and said designers will have to continue creating low-resolution graphics for the foreseeable future.

In the current climate, Mills told .net, a sensible solution would be separate high-res and low-res sites, or media-query usage to swap assets as relevant: "For CSS resources, you can use media queries to swap between the two. You might have to have nested media queries – two to filter hi-res and low-res devices, and then child media queries inside those to start changing layout for different screen sizes." For HTML, Mills said the problem is harder, and he considered adaptive-images.com by Matt Wilcox the best solution, for most situations. (Wilcox has also recently written a feature for Opera on responsive images, providing further insight.)

Increased costs

Mills also agreed with the suggestion that Retina displays could introduce another 'tax' on development, in the sense of increased costs to clients. "Having to create more complicated CSS and separate low-res and high-res images sets will definitely increase costs," he said. He added that he hopes CSS3 features such as gradients and shadows will reduce the number of image assets required, and suggested educating clients by providing sets of test pages with and without high-res images. "Show them to clients on low-res and high-res devices," he advised, "to illustrate what the problem is and what is needed to get around it. Because – at least for the moment – 'hi-res device' means 'iPad/iPhone/MacBook', which equals 'sexy', the sell should probably not be that hard!"

Riley, however, told .net that while he's thinking some time into the future, we will eventually reach a point, by whoever happens to be the editorial authority on the matter, where high-res is the global 'norm': "And designers and engineers aren't going to want to waste their time downscaling or pixel-fitting UI assets for the legacy 1x screens, so they will be neglected. Either they'll be served 2x—at a quadrupled bandwidth cost—or they'll be neglected altogether. We've seen web developers do this with IE6 all the time. I know there's a difference between downloading a new browser for free and buying a $1-2k computer, but time has a funny way of making people apathetic about those 'minor details'."

He therefore hoped that the industry will be able to find a way to only design at 2x, "assuming engineers and designers will lead the pack in Retina adoption, and have software intelligently scale most assets—whether they be raster or vector", which would smooth the transition. In the meantime, while Riley wouldn't recommend anyone grab a new MacBook Pro today just for Retina, he called it a "no brainer" if you're in the market for a new computer: "The only caveat, however, is you have an external monitor at 1x—non-Retina—for non-HiDPI work."

9 comments

Comment: 1

An interesting article but you really can't compare a tax on IE and a tax on design at 2x (actually anything from 1.3x - 2x as many devices support different pixel densities).

Devices with 'retina' displays will also have modern browsers on them. Moving to tackle 2x displays means a move towards ditching images altogether and towards SVG and icon fonts. This means designers don't have to worry about what the pixel density is.

The issue with IE is that most incarnations – while good at the time – are lacking in today's modern web climate. Fixing broken layouts and quirky behaviour as well as having to deal with backwards compatibility with new browser features is much more labor intensive than using background-sizing and an image double the size of the original (if you stick to using images).

So, to have a 'tax' to design just for 1x (or 2x depending on your preference) devices is ridiculous as in the near future (or now: http://dbushell.com/2012/04/03/svg-use-it-already/), we'll all be using SVG.

Comment: 2

@craigmdennis I know the taxes on IE don't directly to relate to the taxes on different resolution devices, but I still think the overarching principle is that same.

Also, I entirely agree with you that SVG will help to fix a lot of problems. But what I'm really talking about is photographs, videos, and other such graphics that SVG is not a good fit for.

Comment: 3

I've said it before and I'll say it again; web designers and developers now have to do more 'extra work' because of Apple than they ever did with IE6.

Don't get me wrong, I am more than prepared put in the graft - but this is getting borderline ridiculous.

Comment: 4

Going from '2x' assets to '1x' will introduce some minor issues. Optically, scalling 2x down to 1x isn't going to be such a linear step. Shadows often need to be less intense on a 2x display to get the same impact, for instance (IMO).

I'm not sure it'll be a war, but there's certainly a transition in computing on the cusp, but we'll be optimising '1'x for years and years to come.

In the meantime, I'll probably be returning my rMBP for a maxed-out air. I truly love the screen (close to sRGB), but the sluggish UI, GPU heat, and fact that I can never get a close approximation of a 1x screen (even with subpixel anti-aliasing disabled, for standard AA) is a bit of a dealbreaker. If you're a keen photographer, video editor, or print designer you will be all over this. But for me, someone building and designing web apps - I don't need as much power and I'd rather benefit from having the same visual experiences as most users.

Comment: 5

The war is already here. I'm on the side of not believing that design and development should have to happen on Apple products. On the other side are the hipsters who only design for Retina, use -webkit exclusively and believe Node.js to be the saviour of us all just because they can show it off in the coffee shop.

Comment: 6

The "tax" imposed on IE7 (but not IE6) users was a marketing stunt and was not a tax. This article only briefly touches on the impact on end users when it mentions a quadrupled bandwidth cost. The thing is, *that's* where the "tax" will really come in to play.

For end users, and I seem to recall that's who web developers should be ultimately supporting, targeting high resolution displays without proper fallbacks (whether by using appropriate media queries, scripts, or even SVG) means we are pushing images at four times the file size as a traditional image of the same dimensions. End users on mobile aren't always on high resolution displays, and even if they are, that will eat up data plans that much more quickly (not 4 times more quickly, since the entire web is not all images).

As an end user on a mobile wandering a foreign land looking up the bus schedules or my hotel information using an international data plan, I can guarantee I'll want a way to block high resolution images. Sometimes I just want the text, not the pretty pictures, and chewing my bandwidth to send me what the designer feels is an incredibly important photo of the hotel lobby doesn't do me a bit of good.

Let's forget about ease of work for developers (hoping the industry will soon only design at 2X?). Let's instead consider the needs of the end users and figure out a method for responsive images that works. In the meantime, stop making overly-large images for no reason.

Comment: 7

@aardrian: The 'tax' mentioned in this article refers to a general one, not that marketing stunt—designers charging more to support IE <8. The point here is we could relatively soon see agencies charging more to support 2x, which will then flip to charging for supporting 1x.

Comment: 8

@Craig, I knew what "tax" meant in this context, though I may not have been clear in my response. I heard about this *because* I saw people referring to the IE6 tax when talking about this.

Yes, I do see the risk of agencies applying fees for both ends (2x now, 1x later), but as the people who build these things I think we all need to also counsel our clients on the burden that 2x (now and in the future) puts on end users.

A bit off topic, but taken in context of this quote from the last paragraph I hope my reaction at least makes sense: "He therefore hoped that the industry will be able to find a way to only design at 2x."

Comment: 9

It seems that rather than being about Apple vs. non-Apple devices, it's really just an extension of the responsive images problem. It's not about what devices you support, but more about how you provide the correct asset for each user.

As more hardware manufacturers start to release high-res screens, we're probably going to have to deal with many different screen resolutions - not just 1x or 2x.
August issue on sale now!

The Week in Web Design

Sign up to our 'Week in Web Design' newsletter!

Hosting Directory
.net digital edition
Treat yourself to our geeky merchandise!
site stat collection