It’s finally PRINTED!
June 1st, 2010Who’d of thought XCode developers can’t design perfect interfaces?
May 12th, 2010![]()
Excellent Article on the iPad’s Usability. I’m sure Steve Jobs is surprised his XCode developers haven’t created optimal interfaces. I’m sure with a few more license changes, this will all get sorted out.
Wacky Interfaces
The first crop of iPad user apps revived memories of Web designs from 1993, when Mosaic first introduced the image map that made it possible for any part of any picture to become a UI element. As a result, graphic designers went wild: anything they could draw could be a UI, whether it made sense or not.
It’s the same with iPad apps: anything you can show and touch can be a UI on this device. There are no standards and no expectations.
Worse, there are often no perceived affordances for how various screen elements respond when touched. The prevailing aesthetic is very much that of flat images that fill the screen as if they were etched. There’s no lighting model or pseudo-dimensionality to indicate raised or lowered visual elements that call out to be activated.
In contrast, long-standing GUI design guidelines for desktop user designs dictate that buttons look raised (and thus pressable) and that scrollbars and other interactive elements are visually distinct from the content.
The traditional GUI separation between “church and state” — that is, between content and features or commands — has carried over to modern Web design. Those 1993-style image maps are long gone from any site that hopes to do business on the Internet.
The iPad etched-screen aesthetic does look good. No visual distractions or nerdy buttons. The penalty for this beauty is the re-emergence of a usability problem we haven’t seen since the mid-1990s: Users don’t know where they can click.
For the last 15 years of Web usability research, the main problems have been that users don’t know where to go or which option to choose — not that they don’t even know which options exist. With iPad UIs, we’re back to this square one.
Inconsistent Interaction Design
To exacerbate the problem, once they do figure out how something works, users can’t transfer their skills from one app to the next. Each application has a completely different UI for similar features.
In different apps, touching a picture could produce any of the following 5 results:
- Nothing happens
- Enlarging the picture
- Hyperlinking to a more detailed page about that item
- Flipping the image to reveal additional pictures in the same place (metaphorically, these new pictures are “on the back side” of the original picture)
- Popping up a set of navigation choices
The latter design was used by USA Today: Touching the newspaper’s logo brought up a navigation menu listing the various sections. This was probably the most unexpected interaction we tested, and not one user discovered it.
Similarly, to continue reading once you hit the bottom of the screen might require any of 3 different gestures:
- Scrolling down within a text field, while staying within the same page
- For this gesture to work, you have to touch within the text field. However, text fields aren’t demarcated on the screen, so you have to guess what text is scrollable.
- Swiping left (which can sometimes take you to the next article instead of showing more of the current article)
- This gesture doesn’t work, however, if you happen to swipe within an area covered by an advertisement in The New York Times app
- Swiping up
iPad UIs suffer under a triple threat that causes significant user confusion:
- Low discoverability: The UI is mostly hidden within the etched-glass aesthetic without perceived affordances.
- Low memorability: Gestures are inherently ephemeral and difficult to learn when they’re not employed consistently across apps; wider reliance on generic commands would help.
- Accidental activation: This occurs when users touch things by mistake or make a gesture that unexpectedly initiates a feature.
When you combine these three usability problems, the resulting user experience is frequently one of not knowing what happened or how to replicate a certain action to achieve the same result again. Worse yet, people don’t know how to revert to the previous state because there’sno consistent undo feature to provide an escape hatch like the Web’s Back button.
Sad day for RunRev developers
May 10th, 2010http://www.runrev.com/company/runrev-blog/
It’s a sad day for RunRev, and all high level language (HLL) developers. In an unprecedented decree by the current King of the Hill, Steve Jobs has declared his tools, and only his tools, can be used to create compiled binary applications for his new favorite pet platform. The Hell with the rest of us. Making matters worse, he didn’t proclaim his intentions to do this until the fourth release of the SDK, thus allowing multiple millions of dollars in new iPhone initiatives and thousands of developers to believe they were right to develop for his platform. It’s not like he was starting some new platform from scratch, and set up the rules from the beginning.
Nope, he changed things when it suited him best– After he climbed the mountain and didn’t need the little people anymore. “Be damned with the rest of you– oh and thanks for your support, UP TO NOW,” is the message he is sending. He couldn’t care less. Screwing his partners, their customers and their customer’s customers.
Honestly, will anyone really be surprised when he does this yet again to Mac OS X developers?
My next phone will be an Android.
Jobs: “Pay attention to our Ads or we lockout your iPhone”
May 5th, 2010Atomic Web: Must have for iPad
May 5th, 2010
At 99 cents, this is a must have for serious iPad users who spend a lot of time surfing. This mobile browser can replace Safari for accessing the web. The two best features are full screen mode and tabs. You can open up as many pages as you like, each in a different tab. And they can even load in the background.
Aromic Web has settings for Privacy, Disabling page advertising, and setting it up to look like a different browser to different websites. This last feature is especially handy for those websites which insist on showing the mobile version of themselves on the bigger screen of an iPad. Highly recommended!“Now you’ve done it!”
May 3rd, 2010
Looks like the Feds are looking into Apple’s developer licensing practices. I wonder how long Apple will leave Jobs’ “Flash Manifesto” up on their website?
Apple Lovefest
April 30th, 2010
Time to spread some love to Apple. Sure, I’m miffed about how Steve is acting like a spoiled brat, trying to dictate terms to developers, but let’s talk about his products for a moment.
Not since I went out and bought the first Mac 128, have I been totally blown away with a technology, than I am with the iPhone. It truly is a magical device, and continues to amaze each day. I suppose I was lucky in that my first iPhone was the 3GS, and moving from my Verizon LG phone to it is like buying a brand new Kabota. Total awesome piece of technology. When I really stop and think a minute, for me the apps are what really make the iPhone great (certainly NOT AT&T’s service– remember I came from Verizon). One of my favorite iPhone apps is FastFinga, a terrific way to jot notes on the iPhone. It’s sorta like a word processor for bitmap text. Hard to explain, but once you get the hang of it, it becomes the go to app for jotting down anything, in meetings, on the plane, sitting in your car. It’s great! Funny though, FastFinga doesn’t look like a standard iPhone app. Far from it. In fact, this very popular app has real issues conforming to any of the Apple HIG’s for iPhone. As one can see by the picture, it’s very different from any app you’ve probably seen anywhere. I doubt Steve Jobs would approve, and I expect that’s the next shoe to drop: the censor police of the app store will also soon become the fashion police for good taste in interfaces– and cool little apps like FastFinga will suffer. Along with you and I. So, I lied. I guess this wasn’t a total lovefest post for Apple.Can Flash Breakthrough Again?
April 30th, 2010Appholes?
April 30th, 2010
Dan and Richard Gaskin both sent me a link to a funny segment last night on the Gizmodo stolen phone thing. It's the first bit. Jon's got it right on this one.








