Having previously covered the
good and the
ugly, now we get to the genuinely bad. These are things that really didn’t work for me when using the iPad.
(1) The button. There is one physical button on the face of the iPad. Mirroring the button on the iPhone, the main button does one of two things: it either exits the current app to the main app-selection screen, or, if you’re already there, it opens a search function. That’s it. What justifies an entire button so apps don’t need a close box and the main view doesn’t need a search icon to tap? I suppose there’s the pragmatic concern that since the iPad doesn’t multi-task (in 2010, no less) if an app misbehaves the user still needs to be able to quit. OK, fair enough, but why make the button have such limited function? It could operate as a general escape, so it would first take you back to the app’s main interface, and once there back to the iPad’s interface. I could have used that a few times. (What if the app crashes, you ask? Just hold down the main button, analogous to a reboot.)
And once you’ve gone to the trouble of putting a button on the face, why stop at one? Steve Jobs seems to have a quixotic fixation with one-button interfaces. Was he traumatized as a child by something with multiple buttons, or does he just have an unnatural kink for making people poke things with one finger? A second button would have really helped with the controlling/viewing dilemma. Watching a video, for example, you mostly want to just look at it so the on screen controls fade away. I’m told that to bring them back you tap, but that never worked consistently for me. I’d tap, I’d whack, I’d press and hold, I’d flick – sometimes I’d get the controls, other times not. In a different app once the controls faded they never came back. A dedicated button would have really helped here (as would a finer-grained escape).
(2) The browser. The iPad seems like it should be the ideal web appliance. You can curl up in a comfortable chair, in front of TV or out in the yard, and surf the information superhighway. I wouldn’t recommend it. The experience was uniformly awful.
The first thing you want to do is search. So you tap on the search field and it opens a virtual keyboard which, although it belongs in the ugly category for UI features, does the job. The trouble starts when you try to do a second search. The search field and keyboard open again, but this time with the last search still in the field. If it had been selected, like it is in most browsers, so typing would replace it that would have been fine, but the insertion point is at the end. The reason became clear pretty quickly – there are no cursor keys on the keyboard. You would think, as I did, that perhaps you select the text by tapping or dragging on it directly, but no dice. The only thing I could do – and what I had to do for every single search – was backspace enough to delete the last one. Even if I just wanted to change one letter I was forced to backspace to the edit point and retype the string from there. It’s hard to understand how something so basic is so flawed.
Once you get to a page you run head-on into the controlling/viewing dilemma again. Here it’s much more serious than in a simple movie player. As usual the multi-touch navigation works beautifully. Gesturing to scroll and zoom is intuitive and fast, and the text and graphics resolve quickly and clearly. The problem is that most web pages are covered with links, and if your finger lands on one of them accidentally you are whisked away to some random location in cyberspace. The borders of many websites are particularly thick with active regions, so just holding the heavy device would often trigger links as the support hand strayed into the sensitive area. As result, scrolling a web page was like navigating a minefield, trying to find inert space for fingertips and ready to pounce on the back button when I invariably followed an unintentional link. The first time a link opened a new window I was really longing for that general escape ability as I tried to figure out how to get back to what I had been trying to read.
It turns out that even areas without links can be active. The browser allows you to select text, as it should, but this is done by swiping a finger over the text to select, which is the same action used for navigation. I never did get the hang of why it would sometimes scroll and sometimes select text; it’s a mystery forever beyond my understanding. Once text was selected it would put up more buttons and widgets for manipulating it, making it even harder to find an open spot to tap to get rid of it without jumping along a random hyperlink.
Finally, this is Apple’s own browser app so why doesn’t it respect the iPad’s orientation like everything else? Many other apps would reshape their content as the device was turned, but the browser stayed strictly in landscape mode. It would have been much nicer to read long columns of text in portrait mode. Not a huge deal, but again it detracts from the experience in a way that seems sloppy and unpolished.
To wrap up, the iPad shows that there is probably a niche between phone and laptop for a flat device with elegant touch-screen UI. Unfortunately the iPad isn’t it, not at this stage. There are three main things I’d do for version 2, or for a competitor. First would be to make about half as heavy, even if that meant a reduction in runtime. Second would be to add grips of some kind, so it can be easily held with one hand without interfering with the screen. Third, and this is the main one, I’d add a physical button for toggling between viewing and controlling. In the view mode the basic controls would work, like navigation or touching explicit buttons, but nothing would get in the way of watching your video or reading your web page.
In the control mode, which could be activated intermittently by placing the button in easy reach of the hand holding the handle, more controls and gadgets would overlay the content, perhaps providing menus or palettes for performing multiple functions. If you need to rewind the video a few seconds you’d hold down the button to bring up video controls, drag to rewind with the other hand, and then release the button to hide the controls again. If you’re viewing a picture and want to make changes you press and release the button to toggle into control mode. Then you’d have control overlays for adjusting levels or doing other markup.
Apple probably won’t do that due to Steve Job’s deep-seated button phobia, so thinking beyond one button will have to rest with someone else. And while you're at it, make the damn thing multi-task for crying out load.
- jack*
Recent Comments