1 Comment

The Art of Doing ‘Nothing’


“When you do things right, people won’t be sure you’ve done anything at all.” This line from Futurama perfectly sums up how I often feel about my job. Designing, if done right, takes the challenge of communicating a complex idea effectively, and turns it into something that can be easily understood by the masses. When designers do their job right, the overall design fades into the background and you just “get” what you’re looking at. It speaks to you on a fundamental level, things just click and you usually see big smiles on the faces of those who interact with your work.

Through the years, I’ve learned the job of the programmer is much the same. Although my programming abilities are limited to rough forms of HTML and BASIC (yes, BASIC), through my position at the Iconfactory, I’ve learned much about what goes into making a successful software application. I see the challenges that our programmers tackle every single day and I for one am always impressed. This is particularly true of our latest effort, the retina compatible version of xScope for Mac OS X.

When Apple’s stunning new display was announced, I was excited about the increased level of detail and clarity the technology would bring to the desktop. The images are gorgeous, text is as crisp as the printed words and colors are deep and rich. Designing for this display means tools that can work correctly with it, giving you accurate and flawless information from which you can build your designs. From the get-go we knew that xScope, our utility for measuring and inspecting the screen, had to be updated for this new display. What we didn’t realize when we began was just how complicated that update would be.

I’m going to be completely honest here and say that even today, after several months, I still can’t get my head fully around the concept of pixels vs window points. Oh, I know what they are and why they exist, but from the time I first learned how to use a mouse, I’ve always dealt with pixels as the unit of measure on the screen. My entire professional career has revolved around the humble pixel and as such it’s been difficult coming to grips with the fact that the days of seeing exactly what you get on screen are pretty much over.

But all of this pales in comparison to the work that my friend, our lead engineer Craig Hockenberry, had to do in order to get xScope working properly with the new retina display. Whenever Craig starts waxing programatic about his coding, my eyes usually glaze over. That said, there were times during the xScope retina conversion when I thought I was going to go catatonic. If you’re the type of person who loves coding, or maybe needs something to read to send them off to sleep at night, head on over to Furbo.org and read Craig’s technical post on the problems with coding for retina. Suffice to say it’s beyond me. Also beyond me – all the math, logic and problem solving needed to surmount this incredible challenge. I have tons of respect for anyone who finds mathematics fun and exciting, and even more for friends like Craig who wield it like a weapon in the service of their job.

When designers and developers use xScope on a shiny new retina Macbook, all they’ll know, indeed all they’ll care about is that the app works as advertised. xScope will give them the data they need to make their apps and designs the best they can be and that is all that matters. Because of the efforts of Craig and Corey Marion, xScope’s lead UI designer, the app just “works” and it works well. Users won’t know all the algebra and bug finding that went into creating it, but I thought it was appropriate to take just a moment and recognize the hard work that went into making it a reality. I sincerely hope you find the new version of xScope as powerful and useful as all of us have. But the best part is if we’ve done our jobs right, you won’t be sure we’ve done anything at all.

Retina iPad Roundtable

Rene Ritchie, Seth Clifford and Marc Edwards invited myself and App Cubby’s David Barnard to discuss the new retina iPad last week. Ep. 18 of the IterateTV podcast ended up being a smart discussion of the new devices’s strengths and weaknesses, tools and processes we use to develop for it and our take on the future of resolution independence. I spend some time talking about the Iconfactory’s upcoming retina work on Carcassonne and generally try to keep up with the huge brains of the fine fellows gathered around the microphone. If you design for iOS or just want to hear our take on Apple’s new hardware, check it out.

Don’t Forget the Apple Care

As you head out to stand in line at your local Apple Store this Friday, or place your web orders for the new hotness from our favorite fruit company, do yourself a favor and don’t forget to buy your Apple Care. A friend recently asked me what accessories I would recommend for the new iPad. Without hesitation I would say the most important accessory you can purchase is Apple’s extended protection for your iOS or desktop hardware.

Extended warranties are nothing new of course, and even I hesitate to purchase them for household appliances or electronics, but not so when it comes to Apple Care. Apple does an exceptional job of servicing or outright replacing hardware when it’s defective and covered under Apple Care. Many issues can be fixed with a quick trip to the Genius Bar and those that cannot usually get taken care of in short order after just a few days.

When I bought my 27″ iMac in 2009 I purchased Apple Care right along with it. That $99 decision has saved me close to $1,200 dollars to date. A year or so ago my internal HD failed and had to be replaced which would have cost me over $400 in parts and labor. Then just this week I decided to fix a long-standing display problem with the same computer’s screen where light colors and gradients were being blown out and not visible. The Apple Genius I showed it to had never seen a similar problem before and since it was covered under Apple Care decided to just go ahead and order both a new display and a new video card. Total parts and labor for this trip would have cost me $798, but I pay nothing.

The best news is that with this Friday’s launch, Apple is bringing Apple Care+ to the iPad. Like it or not, the majority of damage to our (mobile) gadgets comes from accidental drops. Apple Care+ now covers your iPad for two such incidents and when the cost of replacing a screen is almost as much as the device itself, $99 suddenly seems like a steal.

Ask any geek who makes the best hardware, who’s products have the highest feeling build quality and they’ll most likely tell you Apple. Never-the-less technology inevitably fails. Hardware breaks and entropy rears it’s ugly head and when it does, trust me you’ll be glad you have it covered – spring for the Apple Care. The alternative is… unfortunate.

1 Comment

You’re Gonna Need a Bigger Screen

Well not necessarily a *bigger* screen, but you will need one that sports more pixels per inch. That is to say if the predictions about the iPad 3 are true then your current desktop setup is about to feel very inadequate when developing for Apple’s mobile operating system, iOS. How so? It turns out that the new iPad’s predicted native screen resolution of 2048×1536 is larger than will fit comfortably on any of Apple’s current desktop hardware. At the Iconfactory I use a dual-display setup of a 30″ Cinema display and a 27″ iMac. Even my 30″ doesn’t support enough pixels to view the iPad 3’s screen (particularly in portrait) and that’s a problem.

When designing or coding for the iPhone and iPad, it’s critical to be able to view your work at a 1:1 ratio. It’s best not to view a Photoshop mockup or Xcode simulator window by zooming out, or compressing the pixels to fit the screen. Doing so makes it difficult to tell when interface elements like buttons, tabs and fields properly align or are positioned correctly. I could go into a long explanation of how the math for all of this works out, but TUAW’s Richard Gaywood and App Cubby’s David Barnard have already done that in fine style. If you’re interested in the ins and outs of screen resolutions then head on over and check them out. For my part, I just want to know how long I’ll have to limp along designing for a screen resolution I cannot see 1:1 without having to scroll around. David suggests that Apple won’t be in any particular hurry to bump up the resolutions of their desktop offerings and I have to say I agree with him.

To Apple, the customer comes first not the developer, which is how it should be. Higher resolution displays will eventually be a great selling point for new desktop Macs (and will solve developers’ iPad 3 problems), but they will undoubtedly take time to bring to market. Recent discoveries in Mountain Lion bolster the theory Apple has been planning higher density displays for some time but that doesn’t mean Tim Cook will be announcing them on March 7th. So if you’re a developer like me, be prepared to feel a bit cramped for a while. How long is anybody’s guess but I wouldn’t hold my breath.