Sunday, June 27, 2010

Tripod mounts for iPhone 4?

Anyone out there? Hello? Seriously, what's wrong with the world?


Thursday, April 23, 2009

Does Tim Cook's "netbooks not computers" angle foreshadow jumbo iPod touch?

Tim Cook spoke about netbooks at Apple's latest earnings call.

Quoted all over the web, his comments are as follows:

For us, it's about doing great products. When look at netbook, cramped keyboard, terrible software, junky hardware, very small screens, just not a consumer experience. Not something that we would put the Mac brand on, quite frankly. It's not a space, as it exists today, that we're interested in or that customers will be interested in long term. But do look at the space and see how customers respond to it. People who want a small computer that does browsing and email might want to buy an iPod touch or an iPhone.

If we find a way that we can deliver an innovative product that really makes a contribution, then we will do that. We have some interesting ideas in this space. Product pipeline is fantastic for Mac. 17 out of last 18 quarters, have exceeded market rate of growth. Quite an accomplishment in this quarter, especially when compared to very low-priced netbooks "that I think it's a stretch to call them a personal computer" which are propping up industry.

OK, what's the take home message here? Allow me to translate it from Applespeak for you.

  1. Netbooks have small screens and cramped keyboards, which we don't like.
  2. We won't make netbooks, we're filling that space with the iPhone and the iPod touch.
  3. We will attack that segment with something else too (unless Steve cancels it).
  4. Netbooks aren't personal computers.
Okay, numbers two and three are easy. (Why am I so sure about three? Well, I think Tim Cook goes the closest possible here to announcing future products without actually doing so. Compare this to how Peter Oppenheimer confirmed the iPhone one year before its launch by saying as little as "we're not sitting around doing nothing.")

But how about one and four? I think the real hidden messages are buried in those two.

So netbooks have small screens and cramped keyboards. Of course: that's how big they are! Obviously, a 14" netbook wouldn't be much of a netbook now, would it?

So how to make a netbook-like device that doesn't have a small screen or a cramped keyboard, while keeping it small?

Easy. By making it an oversized iPhone. An Apple tablet. The whole thing will be a screen, and a touchscreen at that, with the possibility of showing on-screen keyboards.

And finally, what about the "not a personal computer" comment?

It's obviously bullshit, for one. Why wouldn't a device with PC hardware (matching the capabilities of a top laptop from a few years back), running a full-blown PC operating system, be a personal computer?

Commenting the earnings call, Jason Snell sees it this way:
Boom! Tim Cook destroys the Netbook world again. "I think it's a stretch to call it a personal computer." Ouch. They've said much of this before, but it's very clear that Apple wants us to know that they're looking at this category and have some ideas... just nothing to announce today.
Well, I beg to differ. Not about the fact that Apple has some ideas, no. But I don't think Tim's comments were meant to belittle the netbook sector. No, I think what he's trying to say is something like this:

What we're going to release in that sector won't be a Mac, it won't be a real personal computer. And I know people will whine about that, comparing our product to netbooks, which are PCs. However, if we keep repeating that netbooks aren't PCs, it might actually start looking true, so people will stop whining.

So there you have it. A tablet device is coming, and it won't be a Mac. It couldn't be: if it were, people would start running all sorts of Mac software on it, and most of it would run very poorly on such an underpowered little thing.

So it will be something based on the iPhone OS. Hopefully, with enhanced functionality, though. Multiple apps, a true file system, saving documents, menus, windows, and so on... The possibilities (and the questions) are legion.


Friday, May 23, 2008

Questioning Tog: Does the Mouse Really Rule?

Did you hear this one? According to Tog, the keyboard feels faster than the mouse, but it's actually slower. (This came via Tim Bray and John Gruber).

Tog says Apple spent $50 million on user interface related R&D by 1989, and learned, among (hopefully numerous) other things, that:

  • Test subjects consistently report that keyboarding is faster than mousing.
  • The stopwatch consistently proves mousing is faster than keyboarding.
Tog's explanation: using the mouse is easy and boring, so it feels slower than recalling keyboard shortcuts, even though "the stopwatch will tell you" that it's actually faster.

No matter how many times I've read this very general statement, it never sounded right to me. Nobody seemed to ever mention any details. When I finally took the plunge and read Tog's actual analysis (parts 1, 2 and 3), I found out that the details still weren't there.

I would really like to know the answers to the following questions, for example:
  1. How many different functions did the subjects have to perform in these tests?
  2. What exactly did accomplishing a task by "mousing" and by "keyboarding" involve?
  3. How many key combinations did the user have to remember for a test? How difficult were these key combinations to enter? How easy were they to remember?
  4. How many mouse targets needed to be acquired, how big were they, and how far apart were they positioned?
  5. Did the users have any previous experience with acquiring similar mouse targets to those featured in the test?
  6. Did the users have any previous experience with using similar (or identical) keyboard combinations to those in the test?
  7. Was the user manipulating an object (like a text box or an image) between these "tasks"? If so, how big was the visual representation of this object? Did the user have to return to the object after acquiring the target needed for the task? If so, was it also timed?
I think Tog's "mousing is faster than keyboarding" statement is akin to saying that "walking is faster than driving," and neglecting to mention whether you were running your tests on a speedway or in a staircase.

Tog's test revisited

Tog does provide us, though, some insight into the methodology of at least one of his tests in the third part of his discussion:
The test I did I did several years ago, frankly, I entered into for the express purpose of letting cursor keys win, just to prove they could in some cases be faster than the mouse. Using Microsoft Word on a Macintosh, I typed in a paragraph of text, then replaced every instance of an "e" with a vertical bar (|). The test subject's task was to replace every | with an "e." Just to make it even harder, the test subjects, when using the mouse, were forbidden to just drop the cursor to the right of the | and then use the delete key to get rid of it. Instead, they had to actually drag the mouse pointer across the one-pixel width of the character t o select it, then press the "e" key to replace it.

The average time for the cursor keys was 99.43 seconds, for the mouse, 50.22 seconds. I also asked the test subjects which method was faster, and to a person they reported that the cursor keys were much, much faster. This was a classic example of the difference between subjective time (the passage of time the user experiences) and objective time (the passage of time the clock experiences). Put simply, the more mentally engaging the task, the shorter the time appears.
While I'm not a user interface expert, this passage leaves me scratching my head. It does seem to prove an interesting point on perception vs. reality, but it definitely fails to prove that the mouse is faster in general.

All it proves is that acquiring targets (vertical bar characters) scattered over a large area of the screen is more efficient with the mouse than with the keyboard. As we'll see in a minute, moving to smaller distances (especially single steps) would be much easier with the keyboard.

The same way, if you need to pick up 20 parcels which are miles apart, you'll probably take a car or a bike, but not if the same parcels are placed on the first 20 steps of a staircase.

As the vertical bars can be pretty far from each other, moving your pointer between them constitutes a significant part of the test, so it should favor the mouse, the faster vehicle – so I thought. But when I ran the test* on myself as a (somewhat questionable) test subject, using TextEdit and a paragraph from an Ask Tog article, I got the following results:
  • Mouse: 143 s
  • Keyboard: 133.5 s
I simply kept pressing the right arrow key until a vertical bar came up, at which point I selected it using Shift-Right arrow, and replaced it by pressing the "e" key. Surprisingly, and contrary to Tog's data, it was actually the keyboard that turned out to be marginally faster in this test.

By the way, having performed this test, I really fail to see how much it has to do with what Tog calls the "high-level cognitive function" of deciding "upon which special-function key to press." Maybe I'm really smart, but I didn't find that holding down an arrow key would tax my cognitive capabilities that much.

I also noticed how unnatural it felt to be using the mouse for the task. I was struggling to exert the right amount of force needed for precision alignment. It felt unbelievably tedious and even physically painful – my right wrist actually hurt afterwards. (Could all this suffering be another reason why using the mouse for the task seems longer than it actually is?)

*These test results are meant to serve little more than entertainment purposes. One (biased) subject, who happens to be the same person who devised the test, is less than statistically convincing. Yet I've made efforts to make these tests as meaningful as possible. I performed every task several times, and averaged the results. When I felt that fatigue, proficiency achieved by practice, or other factors interfered with my results, I kept re-doing the tests, switching their order, and sometimes taking long breaks from them, until I found that my results stabilized around a value, and that any difference between the values I got for the two or three tasks I was comparing was representative rather than accidental. I also honestly tried to achieve a reasonably good score in each test, without going into extremes. (I basically pretended that I had to perform actual work, in an office setting, on a looming deadline. I'm an average typist, and a power mouse user, having spent a decade working in Photoshop, Illustrator, InDesign, and Final Cut Pro, all particularly mouse-heavy applications.)

The mouse fights back

It occurred to me later that my results may have been affected by the font size I happened to be using. It was 13 points (Verdana) on a 17" screen at a 1440 x 900 resolution; Tog might have used a larger font and/or a smaller screen resolution almost two decades earlier.

Sure enough, setting the font size to 22 points turned the results around, improving the speed of the mouse by a large margin, and letting it score a narrow victory over the keyboard (though nothing like the double speed that Tog reported). Keyboard times also improved a bit:
  • Mouse, large font: 113 s
  • Keyboard, large font: 122.5 s
So Tog seems to have neglected a very important factor in his keyboard vs. mouse test: font size. Larger mouse targets are obviously easier to acquire, so the point size of the text you're editing can decide which method is better or more efficient.

That got me curious. What happens if we increase the font size to a ridiculous 200 points? I found out that the difference between the mouse and the keyboard almost disappeared in this dreadfully impossible task. In addition, the test results varied greatly, and repeating the test again and again helped improve times by leaps and bounds as I learned new tricks on the way. The keyboard started to win again, though mouse performance improved by a small margin every time I repeated the test. I averaged the results when I felt that the curve of the mouse improvements was flattening out:
  • Mouse, huge font: 155.5 s
  • Keyboard, huge font: 133 s

Beating the test

But there's more. Trying to speed up my "keyboarding," I tried the Alt-Right Arrow key combination, which jumps one whole word ahead, making navigation faster – and stumbled upon a "cheat": TextEdit considers the vertical bar a word boundary, thus whenever one shows up, Alt-Right arrow will stop the pointer right before it. Using this cheat (which involved more cognitive brain functionality, as well as some keyboard acrobatics), I needed more concentration than before, so the task felt much more difficult, and I also had to stop and correct some errors (something I didn't have to do using the other two methods). However, it cut my keyboarding time by a fourth, beating the hell out of the mouse at both normal and large font sizes:
  • Keyboard "cheat," normal font: 95.5 s
  • Keyboard "cheat," large font: 94.5 s
Noticeably, increasing the font size did nothing here. My theory is that finding each vertical line character was somewhat automatized by the cheat, so better visibility wasn't much help.

One side effect of the cheat was that I ended up inadvertently typing a lot of uppercase "E"s. I think the reasons are that here (1) I had to use two modifier keys (Alt and Shift), (2) I had to switch between them pretty fast, and (3) almost every second navigational keystroke (i.e. Alt-Arrow) was followed by a selection (Shift-Arrow), then immediately by a replacement ("e") keystroke, requiring me to switch between three different key commands very often, making me mess up one of them a lot.

Using a huge font size slowed down this task as well, but it was still the fastest way at that size:
  • Keyboard "cheat," huge font: 123 s
The table and graph below summarize how the font size change affects the three input methods tested. The straight lines connecting the dots should by no way be interpreted as implying continuity, they are provided mostly for better visibility (and as hints at very vague trends).

I could come up with several pages' worth of analysis, comparing and contrasting how font size affects each test case, but suffice it to say that without specifying everything down to the smallest details, it's just about impossible to decide whether the keyboard or the mouse is faster even in a very simple test like this. Tog seems to have oversimplified things a lot.

The keyboard's turn

In order to investigate things a bit further, I also came up with a test of my own, one where I felt the keyboard would have the edge, as it required smaller, more precise navigational movements.

In my test, the subject needed to replace every second letter of every word in a (much shorter) paragraph with the letter "p." I was the test subject again, and these were my results:
  • Mouse, normal font: 137 s
  • Keyboard, normal font: 90 s
  • Mouse, large font: 118 s
  • Keyboard, large font: 76.5 s
Boy, did I manage to contrive a test that favors the keyboard! As expected, it performed better as a means for selecting every second character of a word. Rhythmically pushing the right arrow twice would always do the trick, whereas with the mouse, I had to move past small characters of varying width*, and had to strain myself to position the pointer accurately. It seemed unnatural.

Replacing the letters was identical in both cases, so it didn't influence the results. (Or did it? We'll get back to that very soon.)

Somewhat surprisingly, a larger font size helped both tasks equally well. I expected mousing to benefit more, as the targets became larger, thus easier to acquire. Investigating the reason for this anomaly is beyond the scope of my blog post, but it, again, proves my main point: that things are complicated.

If you think by now that I'm some sort of a keyboard evangelist and mouse hater, rigging tests so that they will always let the keyboard win, then well, you've got that mouse pointer hovering over the wrong guy. No, I'm the guy who keeps rigging tests in small ways that change the results in big ways, trying to show that simplistic statements like Tog's are simply wrong. And ultimately, I just want the help the case of redundancy and freedom of user choice in user interface design.

So then I changed a little aspect of my test: instead of the letter "p," the subject now had to enter the "¶" character in place of every second letter of every word. This turned the test on its head, making the previously victorious keyboard lose by a Tog-uesque 50% margin.

What gives? Well, it's simple. While the subject (i.e. yours truly) could easily rest his fingers on the "p" key while navigating with the keyboard in the previous version, that was no longer possible with the hard-to-reach Alt-"7" combination needed for the "¶" character. Thus, every time I had to switch between entering that symbol and navigating/selecting, I had to lift my fingers off the keyboard and reposition them, losing a lot of time. (With practice, my times improved greatly. From an initial dysmal 184 seconds, which I excluded from my calculations as an anomaly, I reached a much more respectable average of 149 seconds by the time I finally decided to give the whole frustrating mess a rest. As always, the number I provide is an average. However, an interesting trend to note is that this is an initially huge margin that gets significantly smaller with practice.)
  • Mouse, large font: 126 s
  • Keyboard, large font: 149 s

So, guess what? You can't say that "the keyboard is faster." You can't even say, "The keyboard is faster when replacing every second letter of every word in a text." No, you even have to say what character you're replacing it with. It gets as specific as that.

*Switching to a monospaced font didn't help much, though. I ran the test with Monaco, and didn't notice any statistically significant improvements.


After testing some very narrow areas of the huge field of "user interaction by keyboard vs. mouse," all I can say is that both input methods have their strengths and weaknesses, and their optimum fields of use should be analyzed and investigated much more carefully than Tog appears to have done.

Personally, I think it's best to let the user decide what method(s) to use, and provide for both keyboard and mouse-based functionalities, whenever it makes any little sense. But even providing several methods isn't going to be enough: you also have to get them right. Designing key commands and mouse targets is pretty easy to mess up, having the user end up with useless input methods even in their preferred contexts.

Also, even though some specific input methods may have intimidating learning curves, in some cases, they may be worth the effort (e.g. in the case of the iPhone keypad). Obviously, users may be a bit tough to sell on such user interface choices, so they must be explained in a careful and convincing way.

Finally, I also wonder whether it's always speed that matters. It may easily be the case that the faster way of performing a task is more exhausting, less natural, or simply less fun. Speed may or may not be important; the developer simply can't imagine every possible way his or her product will be used. Maybe a task you imagined to be pretty rare as a developer will end up being the one that your user needs to perform a thousand times in the course of two hours – so there had better be a fast way of doing it. And while you're at it, why not also create an easy way, and a fun way? Redundancy can be a great thing in the world of user interfaces.

That is, unless you can find a perfect way, one which is easy, fun, fast and natural in every situation – I'm hard-pressed to find too many examples, though.


Tuesday, March 25, 2008

The Magic Text Field: searching, URLs and bookmarks

Cabel Maxfield Sasser notes how advertisements in Japan display search boxes with recommended search terms, as opposed to URLs. It certainly feels more user-friendly (and natural) to enter real words into one box (the search box) than to type something as geeky as a URL in another box (the URL field), and the author even speculates that future versions of Safari may transition to displaying a more prominent Google field and a less prominent URL field.

This has got me thinking. These are my closely related, highly anecdotal observations on URL entry vs. searching:

  • Some people (especially Firefox users) enter everything, even URLs, in the Google box. (By default, a new Firefox window has focus on the Google box.) These users will have to click again at the Google-displayed URL, but they don't seem to mind.
  • I sometimes catch myself mistakenly using the URL field instead of the Google field, hinting that search may be taking over from URL entry in my use as well.
  • Firefox actually accommodates (perhaps encourages) this previous behavior: entering expressions in the URL box yields Google search results or top hits. Other browsers simply display the predictable error messages caused by such attempts at connecting to malformed URLs.
But then I also have some more loosely related observations as well, mostly concerning bookmarks and history items:
  • I hardly ever use the bookmarks menu for opening a page, relying on the autocomplete feature of the URL field instead. That is, if I add something to my bookmarks, I will navigate to it later by starting to type some words from its URL (if meaningful), rather than choosing it from the menu.
  • But then I hardly ever add any bookmarks either. If I want to bookmark a page for later retrieval, I don't have to do anything: it will be automatically added to the History list, and thus it will be available for autocomplete, too.
  • In Leopard, Safari's history items and cached pages are indexed by Spotlight, even enabling users to find visited pages by searching for words in their contents.
The most perfect solution for me would probably involve one huge box with hooks for a lot of AI magic working behind the scenes, listing Google hits, URL matches, Wikipedia and Dictionary and other results, cached page search terms, all categorized, ranked in an ultra-smart way with the most likely results first, all displayed in real time, with easy keyboard-based navigation possibilities.

I think web pages are verbal, and the most natural way of relating to them is by typing text.


Wednesday, February 13, 2008

MacBook Air: harbinger of the tablet Mac?

As I was re-reading, for some reason, my old post on the November tablet Mac rumors, and got to the part where I speculate on the features of the purported device (such as ports and disk drives), something suddenly occured to me.

As I speculated back then, a tablet Mac would very likely need to do away with some traditional Mac features, such as an optical drive. However, I didn't think it would lack Ethernet or FireWire: I thought those would be too extreme omissions.

Guess what: Apple has just shipped a Mac without any of these things. It remains to be seen how exactly people are going to respond to such a radical elimination of items whose presence in a Mac have been taken for granted for almost a decade, but looks like Apple is on to something there.

The Air is more of a breakthrough in what it lacks than it is in what new features it adds (basically, a MultiTouch trackpad), and I'm sure Apple is eagerly anticipating feedback.

If it turns out that there exists a significant enough class of users who don't mind the radical departure this Mac represents, Apple can be more confident in launching yet another product category: a tablet Mac, taking the Air's ultraportability concept yet one step further.

MultiTouch cannot be forever confined to cellphones and trackpads.


Thursday, January 31, 2008

MacBook Air: iMac or Cube?

The introduction of the new Mac laptop is a bold move by Apple, as the subnotebook radically eliminates some components that may be considered essential.

Every single Mac that Apple has released since 1998 has had Ethernet connectivity, as well as an optical drive. Since 2001, every Macintosh has also shipped with a FireWire port.

The MacBook Air does away with all three.

Sure, there are workarounds, but all are cumbersome. Ethernet is available as a $29 dongle that Apple sells separately, though it would occupy the single USB port of the Air. External optical drives also exist (Apple sells one exclusively for the MacBook Air), but carrying such additional devices around somewhat defeats the purpose of having a super thin, super light notebook. The external drive would also need to fight over the single USB port with competing devices, unless you buy yet another companion product, a USB hub.

You can also hack into the optical drives of neighboring Macs or even PCs with a piece of software that is reputed to "just work," as one expects from Apple. However, it's kind of creepy to be constantly asking favors from fellow computer users, even installing software on their machines, whenever you want to use an optical drive. And those computers had better be equipped with WiFi, too.

And as for FireWire, you're pretty much out of luck there.

So, what the hell were they thinking? How could such a device ever sell?

Well, Apple did make a similarly radical move back in 1998, when it introduced the original iMac. Steve Jobs was back with a vengeance, and he chose a pretty dramatic way to show everyone he means business: he released a sexy-looking, simple entry-level Mac that lacked a floppy drive, and eschewed traditional ports such as SCSI or ADB in favor of USB. So what happened? The iMac sold as hot cakes, and peripheral makers started to build USB keyboards, mice, scanners, etc. The floppy disk was already on its way out, but the iMac's snub might have been the last nail in its coffin. So, the iMac pretty much changed the world around it.

Will the MacBook Air do the same? Will USB flash drives kill optical disks? Will WiFi drive Ethernet into extinction? Is Apple knifing its own FireWire baby?

It certainly looks like Apple would very much like all of this to happen. Just as modems started to disappear from Macs, Ethernet may be next, surviving only in professional machines. Optical drives may still stick around for a while, though, but Apple doesn't think they will be missed from the MacBook Air. While you'll still need to leech the drive of a neighboring computer for software installs, the Mac maker would prefer if you turned to its products and services instead of using an optical drive: get music and video off iTunes, use iPods instead of burning CDs, and buy Time Capsule for backups. Clever.

There certainly is method in this madness. Anyone in the market for a $1,800 notebook must have some cash to burn on these products and services, so each Air sold (especially in countries where the iTunes Store is available in its full glory) should generate some guaranteed extra revenue for Apple. Besides, these relatively wealthy people probably already have a Mac at home anyway, helping them overcome most of their objections to the Air.

If sales of the Air reach a critical mass, the new Mac could help reform the computing landscape, just like the iMac did a decade ago. If sales end up failing to go off the charts, but remain respectable, then, well, Apple can still boast a successful niche product, and I'm sure that a hundred bucks or two may go off the price eventually, if needed.

But what if Apple has made a major miscalculation, like the one in the case of the Power Mac Cube? Wasn't it also a relatively underpowered pro-level Mac that the market deemed too expensive? Pundits crucified the Cube for putting style over substance, and weak sales of the radical-looking new Mac spelled serious trouble for the still-vulnerable Apple.

I don't think there's any reason to anticipate a similar fate for the MacBook Air. There may be some superficial similarities to the Cube, but the differences are more significant:

  • As far as tech specs go, the Cube was clearly a weaker product than the Power Mac, yet it cost more. The MacBook Air is also a weaker product than the MacBook Pro, but it costs less as well. (However, it may also be compared to the MacBook, and it wouldn't fare so well in that comparison: the Air is the less capable and more expensive of the two notebooks.)
  • Miniaturization is not such a strong selling point for a desktop Mac as it is for a notebook. The beauty of the Cube was mostly skin deep, whereas the thinness of the Air is also very practical.
  • Apple's revenues in fiscal 2001 were $5.65 billion, whereas in 2007, they were $24 billion. Apple can better afford to risk less-than-optimal initial sales of a new experimental niche product now than it could at the time of the Cube.
I definitely don't think one should worry too much about the fate of the Air. It may not necessarily become a second iMac, but it really shouldn't be a second Cube either.


Thursday, January 24, 2008

Yet more whining on Apple secrecy

I'm sure Jens Alfke is a great guy and a great engineer, and I understand if he leaves Apple due to creative differences. Yet some of his comments seem to warrant a big "Duh!"

I think Apple’s policy on blogging is one of the least enlightened of major tech companies; Microsoft in particular is surprisingly open.
Well, Apple has been all about secrecy for the past decade or so, while Microsoft, perhaps the world's greatest vendor of vaporware, has always embraced blabbering as one of its main communication tools. Isn't it as simple as this?


Sunday, December 02, 2007

E-book readers: they look good on paper

There's been some talk about Amazon's new Kindle e-book reader being the "iPod of books." This analogy might be cute and catchy, but it's deeply flawed, and wishful thinking at best.

First, being the iPod of books is a very ambitious undertaking. Much more so than being the iPod of music. Here's why:

  1. With the iPod, the content that the device was built for is music. The display is only an organizer for it. The actual presentation of the content is audio playback. With an e-book reader, however, the display has to serve not only as an organizer, but also as the actual presentation canvas for the content itself. And that's hard, because
  2. electric devices have been able to play back music for decades. Most users were already satisfied with the sound quality of existing MP3 players even before the iPod debuted, so Apple's device didn't need to achieve a technological breakthrough in its core competence of music playback. However, no electric device exists today that could "play back" a book or a newspaper at an acceptable quality. Therefore, a successful e-book reader will need to break new ground.
  3. Listening is passive, while reading is active. Listening to a song only requires you to push the play button, and the rest will just happen to you. However, reading a book requires constant and conscious interaction: not just scanning the text with your eyeballs, but also physically navigating the book by turning pages.* A device for reading has to facilitate that as well in a very humane and user-friendly way, not to mention providing additional functionality such as annotation features**.
*What if an e-book reader could automatically scroll, tracking your eyeballs?

**This blog post of mine is serving me as a great lesson about procrastination. I've been working on it for over a week, and in the meantime, several other web authors have posted their opinions, which are in some cases very similar to mine. Ars Technica's John Stokes, for example, mentions annotation features, as well as several other points I also visit.

The Muzak of Books

But there's more on the iPod analogy front. The music you hear on an iPod is comparable to what you hear on your stereo. Sure, the quality is certainly not the same as on a high-end device, but it's is acceptable for the vast majority of users, most of whom would be hard-pressed to tell much of the difference anyway.

However, just imagine, for a moment, an iPod that could only play a MIDI version of any song. You would hear your favorite songs arranged for generic software instruments, and some machine voice would do all the vocals.

Would this device be a hit? Would you buy it?

I'm asking because this is more or less what Kindle, or any other e-book solution on the market today, does. What it presents is nothing but the MIDI version of a book. Layout is generated on the fly, using a generic font. Sure, the original words are kept, just like the original notes in a MIDI version of a song. But yet it's not the same song, and it's not the same book. It's the Muzak version of a book. It looks more like a webpage. Compared to the real thing, it's an abomination.

Readers want the real thing; the book as it has been designed and laid out by design professionals.

Sure, Muzak has its place in elevators and public toilets, but it's not the music you love, it's not what inspires your kids to write fan mail. And the same way, Kindle is perfectly suitable for reading an end-user license agreement or a shopping list – but not something you care about, not something you grow attached to.

A book reader? That's me!

And finally, there's a third thing. Your iPod does not equal to the music on it. The two are very separate things. An iPod is just the device that plays your music. The music is something you cannot touch, wherever it's coming from. A band, a stereo, a clock radio, an iPod: these are sources of music, you never think of them as the music itself. You don't even think of a CD as the music itself: it's just a recording that you have to get music out of by playing it in some device.

It's not that I have a penchant for stating the obvious, but this is a very important difference between music and books. Books have a physical representation that music or films lack: they are objects. The volume that you hold in you hand isn't a "source of book," or a "book recording" that you have to "play back." Nope. It's the book itself. It's a thing.* You need eyes and hands to read it, no other devices are necessary.

*Again, someone else has said it better as I was plugging away with this post. Damn.

Envisioning a device that will one day complement, substitute and perhaps even replace paper-based books, and calling it an "e-book reader" is a mistake. If such a device is to emerge, it won't be "playing back" a book: it will have to be the book.

I picture a featureless, lightweight, white or semitransparent, sublime-looking object, about the weight, size and shape of a book. Its surface would appear to be paper-like, with text and images apparently printed on it: it would show a page from a book. (Or maybe a spread. I know that there would be some serious and hard design decisions to be made, like how to accommodate oversized layouts such as a newspaper's.)

Looking at this thing from a distance, you could even mistake it for some high-tech version of a book. Not a reader: you're the reader. It's the book.

You would turn pages by imitating page-turning gestures on its touch-sensitive surface. You could flick it by manipulating its side. It would need to accommodate loads of other familiar gestures, in order to make you feel like you're reading a book (like, half-turning a page to see what's behind it, then turning it back). And the whole thing would need to bring you as much as possible of the whole book experience, such as layout, design, typography, look and feel, and even as many as humanly possible of these partly tongue-in-cheek, yet entirely perfectly valid points.

Maybe the world isn't ready for such a device. Not in the "world's not ready for Vista" sense, but simply because the hardware needed for such a device isn't feasible yet.

Of course, this thing will happen one day. Maybe it will work through directly stimulating parts of your brain to give you a complex multisensory illusion of reading a book, and you shouldn't expect it before 2100. Maybe it will happen next year. But it will be there.

We need to save trees. We need to simplify logistics. We need more interactivity: spoilt by the web experience, how many times did you wish you had hyperlinks or search boxes in a book or newspaper you were reading?

A real-world need

Two years ago, I left my home country. Among various other changes, I'm no longer able to read my favorite newspaper as it's not available where I live now.

Even though it's the year 2007, there's still no technology out there that could help me out. And no, Kindle won't be the answer either.

Back in the days, I would drive to work for an afternoon shift, and I'd make a stop at a drive-in restaurant for an early afternoon breakfast. I would buy my favorite paper, fold it out in front of me, and read it while eating.

I would look at the front page, and see what's above and below the fold. I would look at the teasers, the headlines, the subheads, the captions; the different fonts and typefaces, the weighing of contents by the size and position attributed to them by the editors and designers.

I would subconsciously use the placement of photos, the clever typographic solutions, and all the other subtle ways of presenting all the information and meta-information, to choose which stories I would read, and in what order. To this day, I can recall some of the stories the paper broke years ago, and my recollections are always complete with the entire layout, not just the words and the pictures.

After looking at the front page, I would go in. As I'd turn the pages, some familiarly distinct features would appear, making sure both that I feel at home and that I can find my way.

For instance, there was be the opinion page, one of my favorites. One big editorial, serious in tone, set in boldface (a bit of an assault on readability, but still, I'd grown to like it). A short, rather caustic opinion piece, in a larger font, set in italics. A small box with a short scathing op-ed always by the same guy, day in, day out. And in the center of the page, a large essay on some controversial issue, with an attention-grabbing pull quote: something I was almost certain to read every day.

When I moved halfway across Europe, I was looking for ways to keep reading that paper (which was not available on newsstands in my new adopted home). A subscription was out of the question: both the expense and the delay would have been forbidding.

So I subscribed online. I was looking for the same experience, or at least something similar. But it wasn't meant to be.

It's not just that I was unable to take my subscription to a restaurant. It's not just that I was confined to a computer for reading. All I could access was a page with a list of headlines. I could click on each, and the text would appear in my browser. As would the photos. I could also search, and get yet more clickable lists.

That was it. No layout, no design, no presentation. Just the words and the pictures. It was a website, except that the stories were not written for the web. They were cut and pasted from the paper. It was less than a website, and much less than a newspaper. It united the disadvangates of both.

I despised it and canceled after a few weeks.

Apparently, whoever was in charge of the online version thought that content was the only thing that mattered, where content would equal all the words and the pictures. According to this belief, when you buy a paper, you pay for words and pictures, and that's it. Today's newspapers place these things tediously on pages, requiring a lot of human effort, but that's only because a printed page has a limited capacity, and working with this limitation is hard. In a better, more advanced world, there will be no more paper, therefore there will be no need for laboriously placing the contents on these things called "pages." You would just present a table of contents, and the contents themselves, which are free to flow without any spatial limitation.

Therefore, a newspaper or a book would be just like a webpage, and all you'd do is search, click, and then scroll, scroll, scroll and scroll as you read.

Welcome to the brave new world. Luckily, this will never happen. Anyone who thinks that a newspaper, a magazine, a book, or basically anything that gets printed, is nothing but a sum of its words and pictures is seriously, sadly mistaken, and will not be the driving force behind a successfull e-book concept.

Anyone who doesn't know the vast, incredible importance of layout and presentation simply doesn't get publishing, period.

Anyone who gets publishing knows that an online HTML version of any print publication is not an equivalent of the original.

Apparently, Jeff Bezos doesn't get publishing. He's good at selling books and other things. He's a salesman. He may even be a sales visionary. But that's it.

An acceptable presentation of a book or a newspaper in an electric solution means that it has to look very close to the real thing. It has to make you forget that you're looking at a gadget.

Apple's chance

Currently, the only company that seems to even come close to "getting" things like these is Apple. In addition to its obvious lead in user interface design, its famous dedication to any design, and very specifically, typography, is a clear indication. Remember, the Mac was the device that kick-started desktop publishing in the eighties.

I think, or rather, I hope, that Apple will introduce a device to top Kindle, turning Amazon's attempt into the kind of roadkill that litters the technology highways. Kind of like the iPod did to the likes of the Archos Jukebox.

Three years ago, based on the success of the iPod, I thought Apple could probably be the one company to pull it off.

Now, in 2007, Apple has unveiled Multi-Touch, as well as an embedded version of OS X. If e-books are going to be more than a blip on the radar any time soon, they will be courtesy of Apple, not Amazon.


Tuesday, November 20, 2007

Kindle: damn, they stole my idea. Here's my mail to Steve Jobs from 2004

Naive as I was, I sent the following e-mail to Steve Jobs back in 2004.
Needless to say, he never wrote back.

Dear Steve,

Here's a product/service idea I think Apple could pull off pretty decently.

We all hope that one day lots of trees will be spared by switching from paper to a digital alternative. Yet it's not happening. E-book readers crash and burn. People insist on real books and newspapers, and it seems to be an emotional thing.

Or is it? I think it's just that current devices suck. Apple could, once again, show the world how it's done, and make it a hit.

Here's what I think it needs.

(1) A reader (let's call it an iPad for now) needs to resemble a book. It should look non-technical, white, matte, and just beg to be read like a book. (Most of this is a display thing.)

(2) Once iPad resembles a book (breaking users' resistence), people will see incredible benefits. How about "A thousand volumes in your hands?" Readers easily navigate through book collections, take notes, use bookmarks, etc. (Touch-screen technology and on-screen keyboards should be considered. Miniaturization isn't such a big issue here.)

(3) PDF should be to the iPad what MP3 is to the iPod. Transferring these files for immediate access needs to be a breeze. One hidden benefit: users will stop printing long documents that they'd only read once (like software tutorials). People hate reading on computer screens – this should be a hardcopy replacement, not a computer replacement.

(4) Apple has good enough reputation in the contents business to launch an e-bookstore and get large publishers on board. If this catches on, it can be an even bigger cost saver than AAC vs CD. Not to mention periodicals like dailies that face stiff competition from the Web: they could fight back this way. DRM is needed, natch.

(5) You may want to take the computer partly out of the equation. Introduce a small, cheap flash-RAM dongle that retails free of charge as a supplement to books -- or is sold separately. It contains a DRM-protected copy of the book, and it plugs right into the iPad. You can read it while it's plugged (no piracy). Think about buying newspapers at the newsstands like this, on 1" by 1" cards! Quite revolutionary, saving huge printing costs and time.

That's it. If I got you started, I'll gratefully accept donations.

All the best,

AndrĂ¡s Puiz


Sunday, November 11, 2007

Maybe this iPhone will be an U.S. thing after all?

Despite all the hype, the response to the iPhone in Europe isn't nearly like it was in the U.S. Is T-Mobile happy with 10 thousand units sold in Germany on the first day?!

I hope Apple knows, but Europe is a different market. Mobile telephony was born here. There are several service providers, with competitive plans. People here live and breathe cellphones. They unlock phones. And there is a huge choice of devices. Oh, and the iPhone plans are horribly expensive.

Also, saying that the iPod doesn't enjoy a monopoly like in the U.S. (arguably an important factor in the iPhone's success) would be a huge understatement. The iPod's market share in Germany "hit a high" of around 28% in 2007: nowhere close to U.S. figures.

I wonder if Apple wants the iPhone to be a rock star in Europe, or just a device with respectable sales. In the former case, the company may soon be forced to go back to the drawing board and rethink its European iPhone strategy.