Mobile Device of the Year, 2007

It's very difficult to say what's the best mobile device in a given year, because different people have different needs and desires. The ideal device for me might be repulsive to you, and vice-versa. But most of the computer publications try to make a call anyway. If you read the end-of-year reviews online, you'll probably conclude that the best mobile product of the year was the iPhone. It was cited by the Washington Post, Wired, Business Week, and Tech Republic (which strangely listed it as a business technology product, alongside Salesforce.com and LinkedIn).

Other mobile products getting mentions from major publications included the Nokia n95, iPod Touch, Razr 2, and Blackberry 8800. Amazon's Kindle was the only one that showed up on both best-of and worst-of lists. The best-ofs generally liked the wireless features and screen, while the worst-ofs disliked the closed business model and "eye-poking" industrial design.

I don't agree with any of those choices.

Since people have different needs, I think the best product of the year ought to be the one that best meets needs the needs of a particular group of users. It should be utterly compelling to its own audience. There are several questions to ask:

How efficient is it? Since people use mobile devices on the go, it should do just what the user needs, without any confusion or unneeded features. But there can't be any critical features missing, either.

How well does it trade off size vs. power? Because it's carried on your person, where size and weight are at a premium, it should balance tiny size with reasonable battery life.

How does it look? Because it's effectively a part of your wardrobe, it must look great (or whatever the target customer thinks of as great).

By that standard, I think the best mobile device of 2007 -- in fact, one of the best mobile products of all time -- was the third generation iPod Nano.

Don't get me wrong, iPhone fans. The iPhone is a very interesting and provocative device. There are some beautiful features in the user interface, and I love the turmoil it's causing in the industry. Several years from now we may look back on it and call it the most influential mobile device of its time. But that doesn't mean it's the best product.

To me, the iPhone is more an intriguing statement of direction than a completed product at this point. The lack of 3G is a huge compromise, and Apple obviously didn't think through the third party application thing. If you want a slow mobile browser that also plays music and videos and doubles as a somewhat awkward phone, then the iPhone is great. But for all of the cool highlights in the iPhone, I don't think it's enough to crush the phone industry in its current version. Future versions, maybe. We'll shortlist the iPhone III for product of the year in 2010.

The n95 is also a remarkable product in its own way, and I know it inspires a lot of technolust, especially in Europe. But in my opinion, it's just the latest Swiss Army Knife of the mobile world. Next year there will be another one from Nokia or Samsung or somebody else that has an even higher-resolution camera or maybe an electric toothpick or something, and people will be fawning all over that one. Like a lot of Japanese consumer electronics products, it's not a marvelous product as much as it is a marvelously ingenious bag of features.

By contrast, in third generation Nano is not just the latest model from Apple, it's an elegant culmination of the design work they've been doing for years.

The Nano doesn't look all that great in photographs. It's wider than its predecessor, which produced some criticism when it was announced (Engadget nicknamed it "fatty," which is asinine when you see it in person). In real life, the Nano's shape is compelling. It's much thinner than you'd expect from the pictures -- shockingly thin for something that has a color screen and plays videos. With its heavily rounded corners and brightly colored case, it feels a bit like a high tech chocolate wafer. You're almost tempted to take a bite out of it.





Physically, the Nano is almost all user interface -- the screen and thumbwheel take up the entire front of the device. Until we get flexible screens, the Nano is about as small as you can possibly make a device with its features. This is the endpoint, a form factor that's going to be with us for a while.

The biggest surprise to me about the Nano is the usability of video on it. When it was announced, I thought video was a throwaway feature -- who would ever want to watch video on a screen that small? But the reality is that when you're sitting down, you'll hold a Nano about 18 inches (45 cm) away from your face. At that distance, the screen is about the same apparent size as a 20-inch television (50 cm) at the other side of the living room. It's not like watching a flat panel monster screen, but it's very usable.

I'm not sure yet how much video will be used on the device, or what sorts of video, but that's a general question about mobile video rather than anything specific about the Nano. What I've observed so far is teenage girls using the Nano to watch music videos together, commenting on how cute the drummer is.

And that's just another sign that Apple made a great design for its target audience.

The new Nano doesn't have Bluetooth built into it, or Wi-Fi, or a camera, or a phone, or a hard drive. That probably accounts for why the technophiles online have been so dismissive of it (link). But to me, it's an almost perfect balance of functionality and art. Come back in ten or twenty years and I think you'll find it in design museums, when most of today's mobile devices will be long-forgotten and mildly embarrassing.

What do you think? Do you agree with my choice? If not, what do you think was the best mobile device of 2007?

Another example of why the tech industry and mobile operators don't get along

When you work in consumer electronics, one of the rules that gets drilled into you very early on is that you never do anything to disrupt the holiday selling season. In the US, the month between Thanksgiving and the end of the year can account for three months' worth of sales, if not more. During that time, you don't change prices, you don't alter your ad campaigns, and most of all you don't ever say anything about future products, because that might cause customers to hesitate before making a holiday purchase.

So the CEO of ATT, giving a speech this week in Silicon Valley of all places, says that a 3G version of the iPhone is in the works:

"Has Jobs announced that? I don't think he's announced that, but you'll have it next year."

Not only does he spill the beans, but he acknowledges that Apple hasn't announced it and then talks about it anyway (link). The next day the story is carried by the AP, MSNBC, the Times of London, Wall Street Journal, Bloomberg, the SJ Mercury News (which had the version of the quote above), and 318 other publications according to Google.

In the US, the assessment from a lot of commentators is that this won't have much impact because the iPhone is so popular anyway. Maybe, I guess, although the iPhone isn't sold out, so any loss in sales is still a loss. But in Europe, I think it could be a big problem. iPhone sales there are not going great to begin with, and folks in Europe are generally much more conscious of 3G vs. 2G issues. The acknowledgment that a 3G iPhone is coming could cause a lot of people to hesitate before buying.

If AT&T competed directly with Orange, O2, and T-Mobile Germany, I'd be tempted to speculate that they made the announcement on purpose to hurt the competition. But they don't, so I suspect this is just a case of a CEO who wanted to show that he's not controlled by Steve Jobs but instead demonstrated that he doesn't understand consumer electronics.

Questions about Verizon's new "open" attitude

More than half of the traffic to this weblog comes from outside the US, so there are times when I feel obligated (and a little embarrassed) to explain how the mobile market works here. This is one of those moments.

Verizon, the largest US mobile carrier, made headlines in the US today by announcing that by the end of 2008 it's going to make its network available to any device and any application that the user chooses to install (link).

This will seem remarkable to people living in GSM countries where it's normal to choose any device you want. But in the US, it's an unusual idea. Here mobile usage is split between GSM and CDMA. GSM phones have SIM cards, which technically allow you to switch your account to any phone you want. But in practice, almost no users are willing to give up the several hundred dollar subsidy for buying a phone and service plan together, so they only choose phones that come through the operator.

Things are even more restrictive in the CDMA space, where there are no SIM cards. If you buy a Verizon phone, it can only be used with a Verizon account. Same thing for Sprint.

So Verizon's announcement is a nice change, on the face of it. It's also something of a pleasant shock, since Verizon has the reputation of being the most conservative and controlling US operator. But the announcement's actual impact on the market is going to depend on several questions that Verizon hasn't answered yet:

--How will open access be implemented? Verizon says it's going to define a process by which phones can be certified to work on its network. That could be routine or it could turn into a huge barrier to entry. We also don't know how a user's account will be switched between phones. Is Verizon planning to start installing SIM cards in its phones (something that has been done with CDMA in China)? If not, will you have to take the phone to a Verizon store to get it activated? How much will that cost?

Verizon apparently said something about doing activation through a toll-free number, which could be cool.

--How will the service be priced? Verizon's service plans include recovery of the several hundred dollar subsidy for hardware. You pay for the subsidy as part of your monthly bill. Since Verizon doesn't have to recover a subsidy cost on its open access phones, there's about $10 or more a month that it could pass along to consumers in the form of lower bills.

If Verizon doesn't price the open service lower, what happens to the extra money? Does Verizon pocket it? Or will they offer some sort of rebate on purchase of open access phones?

The answer to this one is critical. The US GSM carriers are technically open, but the subsidy prevents significant sales of alternate phones. If Verizon pockets the subsidy money, very few people will take advantage of the open service. The whole thing could turn out to be a PR gesture rather than a genuine change.

But in the hope that Verizon wants it to be more, here's what they ought to do:

--Make the monthly cost of the open plan lower than a traditional service plan, reflecting the absence of a subsidy.
--Make the handset certification process simple and low cost.
--Make it easy for users to switch their account to a new phone (preferably via a SIM card or website or that 800 number, so they don't have to come to a store).

That's an announcement I'd stand up and cheer for.


Impact on the industry

Until we hear the answers to the questions above, it's impossible to guess how impactful this announcement will be. The most important factor may be how the other US operators react. The best result would be if they start competing with each other to see who can make their network more open. If that dynamic takes hold, competitive forces might drive them to really open up even if they don't intend to.

Amazon Kindle: Not a home run, but an interesting start

By now I assume you've read about Amazon's Kindle e-book device. I think it's interesting and important, but more for its business infrastructure than for the device itself. And I'm not at all sure that it'll be a commercial success, unless it gets a lot more content quickly.


What they announced

Kindle's hardware is a lot like that of the Sony and Iliad e-book readers. I won't bother repeating all of the specs; you can find a good summary on Engadget here and here and in a lengthy Newsweek essay here.

The industrial design of the device looks uninspiring to me. It's made of white plastic, a color scheme that most people associate with ease of use, low price, and limited features. Considering Amazon's strong emphasis on ease of use in its announcement today, I guess the color makes sense, but it's at odds with the $399 price.

I haven't touched a Kindle yet, so maybe it looks nicer in person. But in the photographs its sloping edges and slant-key keyboard do nothing for me. It looks a bit like a badly-carved wedge of Parmesan cheese. There are a total of 54 buttons, controls, and keys on the face of the device, so naturally it looks cluttered. There's virtually none of the lust-inducing elegance of the iPhone; the design screams "utilitarian."

"Is it just me or is that thing one hell of an ugly thing to walk around with?" --Comment posted to Newsweek's article on the Kindle

The design is not necessarily a bad thing; the device is going to live or die based on its usefulness, not its looks. But the lack of a lust factor makes people much more willing to nit-pick its features and price. So far Kindle is rated 2.5 out of 5 stars on Amazon's own website, with most of the negative ratings coming from people who have never even touched the device.


Clever wireless, vulnerable business model

Interesting use of the network. Things get a lot more elegant when you look at the services attached to Kindle. Amazon has built in a radio that talks to Sprint's EVDO data network. Wireless is used to deliver almost all content to the device (except for MP3 files, which sync via a USB cable). This is both attractive and disturbing.

The attractive part is that Amazon can pre-test each Kindle device to make sure they connect to the Sprint network before they get shipped to the customer. This is a huge advantage over WiFi. One of the dirty little secrets of WiFi is that non-PCs often have a lot of trouble connecting to WiFi routers in homes and offices. I don't know why this happens, but I suspect it's because the router vendors test their hardware mostly against PCs, and never find the bugs in connecting to other devices. Trouble-shooting a Kindle that couldn't find the network would be a nightmare, and Amazon has bypassed the whole issue by leaving WiFi out of the device.

I also like Amazon's decision not to hit its users with a monthly fee to access the network. Instead, the charges are embedded in the cost of downloaded content. This means that users who buy a lot of content will be subsidizing the ones who read only a little, but Amazon has hidden the charges so well that I don't think anyone will notice. Kindle makes the wireless network do what it should do: Disappear.

I have two worries about the use of EVDO. The first is that if someone lives outside of network coverage (like at my house) their Kindle won't work properly. I would have preferred to see WiFi included as a backup. The second problem is that because Amazon has to pay for that wireless connection, it has to tax virtually any information transmitted to the device. You can load documents onto the device by sending it an e-mail, but you'll pay 10 cents for every message. That doesn't sound like much, but it's annoying to have to pay anything at all for something that's normally free.

Likewise weblogs: You have to pay $1-2 per month for every weblog that you want delivered to your device. That's understandable if you look at Amazon's expenses, but it's astonishing for something that's free on a PC. What's worse, the most enthusiastic readers -- the people most likely to buy Kindle -- are the people likely to be scanning 20 blogs a day. They won't pay $20-$40 a month just to read blogs.

One workaround would be to subscribe to an e-mail blog aggregator like Feed Blitz and have it send a daily digest to your Kindle. That'll presumably cost 10 cents a day -- $3 a month, for unlimited blogs. That is, assuming Amazon doesn't put a size limit on the messages sent to Kindle.

The relatively closed nature of Kindle has led to some angry commentary on ebook enthusiast sites that you'd expect to cheer the product. For an example, there's an essay on Mobile Read here.


Self-publishing: Nice idea, but...

I was delighted to see that Amazon is allowing authors to self-publish e-books for the Kindle. You just submit them to the Amazon Digital Text Platform, set the suggested price, and Amazon adds them to its catalog (link).

The catch is that Amazon pays you only 35% of the suggested price of the book (link). They keep 65% -- for the amazing service of adding your book to their catalog (basically, they shift some bits around on a server). And by the way, if there is any bad debt, Amazon doesn't pay you any royalties at all on that sale, even though they're the ones who failed to collect.

By comparison, Apple takes 30% of iTunes revenue, and NTT DoCoMo takes about 11% of revenue from content and apps sold over its network.



I'd love to hear from the folks at Amazon if there's a reasonable business justification for keeping such a huge cut of self-publishing revenue, but I think it's probably for two reasons:

--Amazon is greedy, and/or

--They don't want to completely undercut the royalty structure of print publishers (who typically pay up to 15% royalties on a printed book)

Either way, Amazon's royalty structure is outrageous. And it won't last. One of the most important aspects of electronic publishing is its ability to change the wretched economic structure of the industry so authors get the majority of the revenue for their work (I've written about the economics of it here). The change is inevitable, and if Amazon tries to hold its current royalty structure it'll eventually just drive people to other e-book platforms that don't rip off authors.


Will it succeed? It's the content, dummy.

All of the issues covered above will affect the success of Kindle, but ultimately the sales of an ebook reader depend on having a huge library of reasonably priced content -- books and periodicals. Lack of sufficient books is what killed the last generation of ebook readers, Rocket eBook and Softbook (I worked at Softbook for a short while, so I saw the situation there first hand).

Judged by that standard, Kindle is off to a surprisingly mediocre start. There are some promising signs. For example, people don't like paying hardcover prices for intangible ebooks, so Amazon is pricing current best-sellers at $9.99, compared to about $15-$16 for hardcover. There are hints in some articles that Amazon is even subsidizing some books to hit this price. The price difference isn't big enough to make people buy Kindle, but it helps to overcome resistance. Good move.

The problem is in the library of other books. Or I should say the non-library. There are supposedly about 90,000 books available for Kindle currently, which sounds like a lot but actually makes for a poor selection. To get an idea of what was available, I took a quick look at the titles available from several prominent science fiction authors -- Niven, Brin, Asimov, Simak, Vinge, etc. (hey, I work in the tech industry, that's what I read). The selection is quite bad -- for many authors, the only Kindle editions are their second-rate books. Or there are a bunch of individual short stories available for 99 cents each, but not most of the novels. I strongly suspect that Amazon is counting each of those short stories as one of the 90,000 "books," because they are all labeled as books in the website. If true, that means the actual number of real books for the device has been heavily exaggerated.

Try the test yourself -- go to the search page here and type in your favorite author's name. Let me know what you find. Maybe fields other than science fiction have a better selection. I hope so.

There's nothing that makes an ebook customer angrier than paying $400 for a device and then finding that most of the things they want to read on it are not available. The iPod succeeded even though a lot of songs were missing from iTunes at first -- but remember that people could rip their own CD collections, and install MP3s for free. Amazon doesn't have a base of content that its users can shift to the reader, and it charges money for any document transferred to the device. So it has to fill the library on its own, quickly.

I think Amazon has a lot of work to do here.

I'm intrigued that about 16 newspapers and magazines are available for Kindle. Unlike books, newspapers and magazines are viewed as disposable, so people are less resistant to buying them electronically. And getting instant delivery of a weekly magazine is a significant advantage over waiting a few days for it to appear in the mail.

Judging by Amazon's price to receive the San Jose Mercury News (Silicon Valley's Incredible Shrinking Newspaper) on Kindle, prices are about 40% less than print subscription. That's not bad. What I don't know is whether the Kindle editions of the papers and magazines will be the full text of the print version, or just excerpts. If anything's left out, people will be turned off.

Amazon must get a critical mass of content -- meaning a lot more magazines and newspapers, and rapid growth in books. If it can do that, Kindle may finally jump-start the ebook industry. It won't explode overnight, but Amazon has a long history of forcing its investors to wait years for the full payoff on investments. If Amazon can maintain that patience, I think it Kindle has a chance.

But I sure hope they make the next version of it look nicer.

Palm OS on Nokia: Strategy or tactic?

I was stunned today when I saw the press release from Access Company saying that they're giving away a beta version of the Garnet emulator for Nokia's N-series Linux tablets (link).

The Garnet emulator lets you to run most Palm OS applications. So in layman's terms, Access is giving away Palm OS for use on any N-series tablet.

I hadn't previously heard any hints from Access about offering Garnet for other platforms. I thought it was only supposed to be available with Access Linux.

I got excited by the announcement, figuring maybe Access had realized that the real innovation is going to come in the applications layer, not the core OS plumbing. I imagined all sorts of scenarios for what they might be planning:

--How about porting Garnet to some other Linux implementations. Hmm, what comes to mind? Maybe Google's Android? Access would need cooperation from Google in order for the emulator to talk directly to Linux. Would Google help with that?

--There is a need in the market for a mobile application environment that's truly "write once, run anywhere." Might Access intend to use Garnet to compete with Java? That would involve porting Garnet to operating systems other than Linux. How about Windows Mobile and Symbian? How about the iPhone?

--There are several ways Access could make money from this:

  • Give away the emulator in beta but charge for the final version.
  • Give away the emulator on N-series but charge for it on other platforms.
  • Give away the emulator everywhere and make money by selling support software and bundling a software store and taking a cut of the purchase fees for apps (a derivative of the iMode and Acrobat models).

Intrigued by the possibilities, I talked to folks at Access. They shot down most of my speculation. As it was explained to me, this is a tactical move. By porting Garnet to the Nokia tablets they can get some testing for the emulator, and also give a "more interesting ongoing proposition for current developers." (It says something about the momentum for your OS when you feel the installed base of Nokia Linux tablets is an attractive developer target, but I guess you take what you can get.)

Access might try to put the emulator on other standard Linux implementations, but they're very busy working on software for licensees they can't talk about yet, and don't have time to port to anything else, including Android.

That's a shame. In my opinion, there's more of a market for Garnet on other platforms than there is for a Linux phone OS now that Google is giving one away.

But Access believes Google's nonstandard approach to Java and Linux is not going to go down well with the mobile development community. They said Android faces big challenges and a likely backlash.

Okay. I guess only time will tell whether that's justified self-confidence or denial of reality.

Meanwhile, I'll go play with Garnet on my Nokia tablet and wonder about what might have been.