Archive for the 'UI' Category

Curated computing: jargon (sometimes) is a good thing

May 16, 2010

This is supposed to *herald* curated computing. Nonsense.

Curated Computing: Fancy cynical analyst term. Here is Forrester Research declaring a new era (‘Post-iPad’, no less).

A consumer can do anything with a Windows PC or Mac… the iPad operates very differently. [It] works more like a jukebox than a desktop — consumers choose (and pay for) applications from a predetermined set list. Each of those applications is, in itself, also curated; the publisher selects content and functionality that’s appropriate to the form factor, just as a museum curator selects artworks from a larger collection…

Rubbish. ‘Curated computing’ has been Apple’s design philosophy for all this decade – that’s only now making its way into industry consciousness.

But it’s a good thing.

If anything, it indicates mobile manufacturers hitting reality. In the short years after the realization that people wanted to ‘do more’ with their phones, manufacturers packed in as many features as they could. A few really took off (cameras, music players, even email), and most others just didn’t (bluetooth, mobile office packages, bar-code readers).

In another way, it’s a sign of the industry beginning to mature. Even as hardware has gotten more capable (faster processors, storage, memory, larger displays, touch-screens) and networks have invested massively to build capacity, there’s a discernible trend to do less better. Manufacturers are (belatedly?) realizing that a mobile device isn’t a smaller personal computer, but something ‘very personal’. And that very personal is very different from personal.

Which is also why everyone in the industry wants ‘vertical integration’ – control over the hardware, operating system, software platform, applications/content, and network. It’s so that having bet on what (limited) tasks a device will perform, a manufacturer has greater control over the quality of what the customer experiences.

Expect, in the next couple of years, for all major smartphone players (in addition to Apple, RIM, Google) to create (curate?) really great out-of-the-box experiences for the 20% of tasks that matter most – email, web browsing, facebook/twitter updating, maps, and playing music/movies (yes, better than what we’ve seen). Expect new devices to ship with fewer radios and sensors, and very few basic applications out-of-the-box. All other features and applications will be available via an App Store, to which there will be a prominent link on the home screen.

If this sounds very much like what Apple’s been doing with iPhone all along, of course you’re right. Forrester’s just woken up, declared it a trend and slapped on an alliteration.

Footnote: also, this isn’t as global, industry-churning a movement as Forrester would have you believe: the Japanese, for the most part, like cellphones crammed with bells and whistles (TV, bar-code readers,credit cards, suchlike). And this doesn’t look to be changing anytime soon.

About the smartphone category called iPhone-like

January 8, 2010

From an email exchange with a friend asking about the Nexus One (the ‘Google phone’) launch.

Thoughts about the Nexus One’s prospects

Does it have better hardware, a better screen, better battery life, better price, more freedom, better apps, better multitasking, better camera than the iPhone? Yes. Is it the iPhone? No.

People who’ll buy the Nexus One say they want to buy something like the iPhone that isn’t the iPhone, and they’re lying even though they don’t know it. They want the iPhone because it’s the iPhone. And nothing else. When you create in your mind a category called iPhone-like, there’s only one member that’s ever going to be a full, incontrovertible member of that category.

These buyers are going to be disappointed even though they won’t know quite why. They’ll blame it on the phone instead of their own expectations, and demand won’t spike the way it did for the iPhone.

Would I buy it?

I don’t like the iPhone, but I like this current crop of Android devices even less. If, in a (thankfully) fictional dystopian universe I had to choose only between the iPhone and the Nexus, I’d take Apple’s baby (and lament long and hard about the lack of alternatives).

Reason #3: form factor wise no Android device has nailed the iPhone. This is HTC and Motorola and Samsung, not Apple we’re talking about. So there. These firms are known for specs, not sex.

Reason #2: I will not buy a phone with a trackball. Ever. Would you buy a Skoda that featured a manually-operated crank to start the engine? Heck, even Blackberrys have moved on.

Reason #1: Polish. I posit that no one has been able to nail the touchscreen experience other than Apple. Not Palm, Not Android. Not (shudder) RIM and most certainly not Microsoft. Since 2007, for instance, Android phones have been underpowered and have had user experience (UX) issues where the phone hasn’t been able to keep up with text or touch input. Now three years later,

Some animations are very smooth, some are janky as hell. The Nexus One has a faster processor than the iPhone 3GS and has twice the RAM, and yet it still cannot have as fluid a UI as the iPhone OS. This is great proof that your software is key—throwing raw power at things won’t necessarily make them better.

And it doesn’t even have to run Android. Every touchscreen phone apart from iPhone suffers from this.

I think it’s worth demonstrating how Apple nails the experience with an example.

In Mobile Safari, the iPhone browser, if you scroll (swipe) too fast, instead of text you’ll see a chequered pattern – the processor can’t render the text fast enough – but the scrolling experience itself is smooth as ever. Once you stop scrolling, text will eventually appear. On any other mobile browser, the scrolling itself will stutter as the processor tries to render everything.

When you’re using a device all day every day as essentially an extension of your body and mind, stuff like this matters more than features.

I’d pick the iPhone. As, sadly, will folks who upgrade from the Nexus One eventually.

Update (10 Jan 2010): Another example of polish in design:

Other issues that I can’t live with day to day? How do I copy text from non-editable field like an email, webpage, or SMS, or even a 3rd party application? Oh, I can’t. Say what you want about the iPhone not having copy and paste for two years — a joke — it’s the single best implementation on the planet for a smartphone and Google’s approach is almost as bad as RIM’s with the Storm-series.

(From Boy Genius Report, via John Gruber)

The combination that makes iPhone so compelling

January 25, 2009

iPhone is revolutionary not just because of its (multi-touch) touchscreen. There are, after all, other touchscreen phones on the market, and none have achieved iPhone’s popularity. Why?

iPhone is revolutionary not because of its Internet browser. Mobile Safari has limitations that other browsers don’t – most notably the lack of Flash support, no text search, no scrolling to the end, among others. But iPhone users are among the most heavy users of the web. Why?

It turns out that when you put both these features together, you end up with something very different.

The web browser is one of the most mouse-heavy applications on your (desktop/laptop) computer. Maintaining that experience on the mobile phone is tough when you have to manipulate physical keys. Open a web page in a browser on your computer and imagine moving the cursor using only the arrow keys.

Your finger on a touchscreen is the best proxy for a mouse on a mobile phone.

This is, in essence, what makes iPhone so compelling. There are awesome touchscreen phones with average browsers, and great browsers trapped in keypad-based phones. iPhone has managed to bridge that gap. And how.

Two thoughts on mobile touchscreen interfaces

September 9, 2008

At the outset, I’d like to clarify I’m no iPhone or Apple zealot. My interest in mobile touchscreen interfaces has been piqued by my recent purchase of an iPod Touch.

I was playing around with a colleague’s HTC Touch Cruise the other day. The Touch runs Windows Mobile 6.1, and, in summary, is a full-featured smartphone with decent multimedia capabilities. That’s not what this post about though.

It’s about two clear observations I made – that we’re stuck in the late 90s when it comes to mobile touch-based input devices, and that UI designers still use the desktop paradigm when designing for mobile touch screens. While Windows Mobile is what triggered this post, with PalmOS, and UIQ too.

Poke, poke

Turns out that it’s a huge pain navigating the WinMobile interface on the 2.8″ touchscreen with your fingers. The buttons are tiny, the menu options are awkward, and it’s next to impossible to grab and drag a scrollbar. I gave up. It’s clear – the best way to navigate a Windows Mobile is using the accompanying stylus.

But a stylus is a hopelessly outdated tool. Along with the physical QWERTY keyboard for desktops/laptops, the stylus is a tool for mobiles that stubbornly refuses to die. Perhaps it’s easier – and commercially attractive – for touchscreen phone manufacturers to add applications and features than to rework a familiar, though suboptimal interface.

iPhone/iPod Touch have changed that. iPhone may not pack the sheer number of applications the HTC Touch Cruise does, but its interface is revolutionary. It lost the stylus. In fact, with multitouch – flicking, pinching, dragging with multiple fingertips – your hand is more effective than a stylus. You may not agree with iPhone the device (I don’t) – but you have to admit iPhone’s set the benchmark for all touchscreen interfaces.

Honey, I shrunk the desktop

Windows Mobile 6.1 has a task bar, a system tray, a Start button and a drop-down Start Menu. With nested menus. On that tiny 240×320 pixel screen.

After spending a while with the device, I realized that Windows Mobile is essentially a shrunk-down version of the desktop Windows interface. The widgets are smaller, but the paradigm is the same. The result is a cluttered interface and a frustrating navigation experience.

Someone’s psyched the WinMobile team into believing that their biggest strength is that their mobile interface looks just like their desktop interface. That may have been true when mobile applications were very simple, but it doesn’t hold true any longer. It’s hurting usability and innovation.

There have been several calls for this, and I’m going to say it here again – the WinMobile team will do themselves and their legions of developers and enterprise customers a world of good if they rethink their interface.

Note: I think Samsung and LG also have very good touchscreen interfaces. But this is merely an observation from Google Image Search results. Haven’t tried them out first-hand, so no comparisons.