Mobile Opportunity - News And Views from Google MO

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.

The bottom line: Google is now an OS company.

The fact that Google’s recently-announced OS products are aimed at mobile devices and social networking sites is interesting, and I’ll talk about the impact of that below. But it’s secondary. I think the big, really important change is that Google has now jumped with both feet into the middle of the operating system world. That potentially has huge implications for the industry.

The impact will depend a lot on how Google follows up. If it pours substantial energy and resources into its OS offerings, it will be extremely bad news for Microsoft and other companies trying to charge money for their own platforms. On the other hand, if Google doesn’t make a serious long-term commitment, it will embarrass itself deeply. This isn’t like launching a new web application — an OS has to be complete, and it has to work properly in version 1, or there won’t be a version 2.

What they announced

It’s kind of ironic. For years after Google became a prominent web company, people speculated about whether or when it would create its own OS. The logic was that Microsoft has its own OS, and Google was challenging Microsoft, so Google would create its own OS too. But then as the years went by and it didn’t happen, people moved on to other subjects. The speculation died out. But one of my rules about the tech industry is that “obvious” things happen only after everyone in the industry has written them off. So I guess Google was due.

The company has been creeping toward the OS space for a while. Google Gadgets is an API to create small applications that run in web pages, and Google Gears is code that lets web apps run offline, making it easier for them to challenge desktop applications. But they were both relatively low-profile (or as low profile as anything Google ever does). But in the last couple of weeks, Google made two much more assertive announcements:

–OpenSocial is an effort to create a shared platform for applications that can be embedded within social websites (link).

–The Open Handset Alliance is an effort to create a shared platform powering mobile devices (link).

Although they’re aimed at very different parts of the industry, they’re both efforts to create a standard platform where there was fragmentation; and they’re both alliances of numerous companies, with Google providing most of the code and the marketing glue. I think there’s a recurring theme here.

Details on the Open Handset Alliance

Open Social was covered very heavily when it was announced a couple of weeks ago, so I won’t recap it all here. If you want more details, Marc Andreessen did an enthusiastic commentary about it on his weblog (link).

The OHA announcement was today, and I want to call out some highlights:

–It’s built around a Linux implementation called Android. Android will be free of charge and open source, licensed under terms that allow companies to use it in products without contributing back any of their own code to the public. This will probably annoy a lot of open source fans, but it’s important for adoption of the OS, as many companies thinking about working with Linux worry that they will accidentally obligate themselves to give away their own source code.

–Google is creating a suite of applications that will be bundled with Android, but they can be replaced freely by companies that want to bundle other apps, according to Michael Gartenberg (link). There is a lot of speculation, though, that if you bundle the Google apps you’ll get a subsidy from Google. The folks over at Skydeck estimate the subsidy could be about $50 per device (link). That might not sound like huge money to you and me, but keep in mind that mobile phone companies routinely turn backflips to squeeze 25 cents out of the cost of a phone. When you sell millions of phones a year, it adds up.

–A huge list of companies participated in the announcement. That’s not as impressive as it sounds; when you have a well-known brand, a lot of companies will do a joint press release with you just for the publicity value. But a few stood out:

Hardware vendors. Samsung, Motorola, LG, and HTC all endorsed the OS. HTC and LG gave particularly enthusiastic quotes. The first three companies have all been playing with Linux for some time, so I wasn’t surprised. But HTC is another matter — it is the most innovative Windows Mobile licensee, and Microsoft must be very disturbed to see it blowing kisses at Google.

(A side comment on Motorola: For a company that said it wanted to consolidate down on a small number of platforms, Motorola is behaving strangely — it jumped all over Symbian a couple of weeks ago, and now is supporting Android as well. I think it has now endorsed more mobile operating systems than any other handset vendor.)

Operators. Participants in the announcement included NTT DoCoMo (a long-time Linux lover), KDDI, China Mobile, T-Mobile, Telecom Italia, Telefonica, and Sprint. That’s a very nice geographic spread, and ensures enough operator interest to make the handset vendors invest.

–Google claims all Android applications will have the same level of access to data on the phone. That’s pretty interesting — most smartphone platforms have been moving toward a multiple-level approach in which you need more rigorous security certification in order to access some features of the phone. I’ll be interested to see how the security model on Android works.

–We’ll get technical information on the OS November 12, and the first phones based on Android should ship in the second half of 2008.

–Although Android’s first focus is mobile phones, the New York Times reports that it can be used in other consumer devices as well (link).

What it means to the mobile industry

It all depends on the quality of Google’s work and the depth of its commitment. If Android has technical or performance problems, it could sink like a stone. If it doesn’t have enough drivers or has poor technical support, the handset vendors will avoid it. If the developers can’t create good applications, users won’t want it. This is a very different business for Google — handset vendors and operators will not tolerate the sloppy, indifferent technical support that Google provides for its consumer web apps.

If, on the other hand, Google’s platform really works and the company invests in it, I think it could have some very important impacts.

Impact on Windows Mobile: Ugliness. The handset companies endorsing Android are also Microsoft’s most prominent mobile licensees. I doubt any of them are planning to completely abandon Microsoft (they don’t want to be captive to any single OS vendor), but any effort they put into Android is effort that doesn’t go into Windows Mobile. So this is ominous.

The whole mobile thing just hasn’t worked out the way Microsoft planned. First it couldn’t get the big handset brands to license its software, so it focused on signing phone clone vendors in Asia, thinking it could use them to pull down the big guys. But Nokia and the other big brands used their volume and manufacturing skill to beat the daylights out of the small cloners.

Now Google is coming after the market with an OS that’s completely free, and may even be subsidized. This will put huge financial pressure on not just Windows Mobile, but all of Windows CE. Even if Microsoft can hold share, its prospects of ever making good money in the sub-PC space look increasingly remote.

Impact on Access: Ugly ugliness. How do you sell your own version of Linux when the world’s biggest Internet company is giving one away? I don’t know.

Impact on Symbian: Hard to judge. Symbian is the preferred OS of Nokia. As long as Nokia continues to use Symbian, it stays in business. The question is how much it’ll grow. After years of painful effort, Symbian just managed to get increased endorsements from Motorola and Samsung. Now Google is messing with both of them. Japan has been a very important growth market for Symbian, now Android is endorsed by both DoCoMo and KDDI. All of that must feel very uncomfortable. If nothing else, it’s likely to produce pressure on Symbian to lower its prices. And Symbian should be asking what happens if Android turns out to be everything Google promises — a free OS that lets handset vendors create great phones easily. It’s not fun competing against a free product that’s been subsidized by one of the richest companies in the world (just ask Netscape).

Maybe if Symbian agrees to enable Google services on its platform it can get the same subsidies as Android does. It’s worth asking. If not, maybe Symbian should be looking for other places where it can add value in the mobile ecosystem.

Impact on mobile developers: Potentially great. Mobile developers have suffered terribly from two things: They have to work through operators to get their applications to market, and they have to rewrite their applications dozens of times for different phones. If Android produces a single consistent Java environment for mobile applications, that would be a big win. And if it can open up the distribution channels for mobile apps, that would be great as well. We don’t have enough details to judge either outcome yet, and the app distribution one depends on business arrangements that may be outside Google’s control.

Impact on Apple, RIM, and Palm: Probably none at all. A lot of the coverage of Android is positioning it as some sort of challenger to iPhone and RIM.

I don’t buy it.

Apple, RIM, and Palm all make integrated systems in which the software and hardware are coordinated together to solve a user problem. Android, by contrast, is only an operating system. It’s plumbing, not the whole house. Unless Google’s handset licensees magically develop the ability to design for users — a feat equivalent to a giraffe sprouting wings — their products won’t be any better as systems solutions than they are today. The OS hasn’t been the thing holding them back, and changing OS won’t alter the situation.

Android puts interesting financial pressure on Microsoft, but it doesn’t directly solve any compelling user problems. If it eventually drives a great base of mobile applications, that might eventually be attractive to some users. But in that case the systems vendors could just add a copy of Google’s application runtime (it’s open source, they can grab it anytime they want). Or they could host their devices on Google’s plumbing. Palm and RIM might both benefit if they could transfer engineers away from core OS and toward adding value that’s visible to users.

Impact on the tech industry: This isn’t just about mobile phones

I have no access to Google’s internal thinking, but even if it sincerely believes it’s only doing a mobile phone OS, I don’t think it can or will stop there. Technology products often develop a momentum of their own, no matter what was intended at the start. The lines between the computing and mobile worlds are breaking down already, and if Google creates an attractive software platform that’s free of charge, that platform will inevitably get sucked into other types of devices. I’m not saying that Android is going to end up in PCs, but if it’s functional and well supported I think it could end up running on just about everything else that has a screen.

Besides, if you look across all of the recent Google announcements, I think it’s clear that Google has a larger agenda: It wants to break down walled gardens, because they interfere with Google’s ability to deliver its services. It has even developed a standard methodology for attacking them: Create a consortium so you don’t look like a bully, and fund an “open” alternative to whatever is in the way. They are doing it to Facebook, and they’re doing it to Windows Mobile. Google doesn’t even have to make money from the consortium, as long as it clears the ground for its services to grow.

Take a lesson from evolutionary history. The most successful animals are not those that adapt to the environment; they are the ones that reshape the environment to match their needs. I think that’s what Google is doing. It’s going to use open source and alliances to suck the profitability out of anybody who creates a proprietary island that it can’t target.

It’ll be interesting to see if and how Google applies this principle to the upcoming frequency auction in the US.

Or to anyone else who gets in its way.

A quick note on Palm’s decision to cancel the Foleo. To me, the most surprising part of the announcement was Palm’s explanation that it couldn’t afford to create two different software platforms (link).

To translate that from Silicon Valley speak, Palm was building two substantially different versions of Linux, one for future Treos and one for the Foleo. That was a huge surprise to me — I had assumed the company was doing a single version of Linux for both product lines. The overhead cost associated with maintaining multiple platforms is enormous. Even huge companies struggle with it, so in my opinion there’s no way in the universe that Palm was going to be able to afford it.

So it turns out the Foleo was almost doomed from the start. Unless it was a raging success from day one, it wasn’t going to be sustainable economically. When the Foleo announcement failed to set the world on fire, the end was probably inevitable.

Several people have asked what I thought of the recent change in ownership at Palm. I don’t have any inside information, so all I can do is speculate like everyone else, and try to apply the lessons I’ve learned from working at other companies.

Overall, I’m very happy for the folks at Palm, and cautiously hopeful about what this might mean for the company’s prospects. I think this outcome is a lot more encouraging than any of the buyout rumors that were floated in the last few months. Palm’s new part-owners clearly understand the value of systems design, which is Palm’s biggest potential advantage in the market. I think we really need another great systems company to challenge Apple, and I would love to see Palm step up to that task.

Although a purchase by a Motorola or Nokia would have been very entertaining from a soap opera perspective, they don’t really understand systems design, and it’s very likely that they would have digested Palm without a trace. I’m reminded of a joke we used to tell at Apple in the 1990s when there were rumors that IBM would buy the company:

Q: “What do you get when you combine Apple and IBM?”
A: “IBM.”

The other buyout option what was circulating, a full purchase by private capital, would have left the company independent, but with a load of debt that might have been crippling. Hardware companies must have a big reserve of cash to fund inventory and tide them over if they launch an unsuccessful product. I don’t pretend to understand all the terms of the Elevation deal (they’re wickedly complex), but from my perspective it looks like the financials aren’t crippling. I am a little worried about Palm’s cash levels, though; a lot of their current cash is going into the stockholder payout.

A couple of other thoughts on the impact of the deal:

Bye-bye 3Com. Palm gets three very well respected people for its board, and removes Eric Benhamou, the last vestige of the 3Com legacy. Somewhere I have a photo of the Palm and PalmSource combined management teams from just before the two companies were separated. The photo includes everyone in the company from Mr. Benhamou down to senior directors. That was about 30+ people. Every single one of them is now gone. So if you didn’t like Palm’s management back then, you should take another look at the company because it’s now 100% different.

Irresponsible speculation about politics. After a change like this, the standard sport in Silicon Valley is to speculate about what it means for the job status of the people involved. In that vein, the thing to ask is, “Who’s running Palm in the long run?” The weirdest part of the whole Elevation deal is the arrival of Jon Rubinstein as both Chairman of the Board of Palm and head of product development. As Chairman, Jon is technically the boss of Palm CEO Ed Colligan. As head of product development, Jon technically reports to Ed. So Jon is kind of his own second-level manager.

That feels…unstable.

Palm seems to now have a surplus of product leaders. Jon is in charge of product development, Jeff Hawkins is the designated product visionary, and marketing SVP Brodie Keast is supposed to control the product road map, according to the press release Palm issued when he was hired. It’s hard to picture a car with three steering wheels. Who will really be in charge? In the conference call Palm said that Jon would be the execution guy and Jeff the visionary. “The combination of those two guys is one of the most dynamic… combinations on the planet.” Maybe. Any organization structure can work if the people involved get along well, and I presume they would not have made this arrangement unless they were all comfortable they could work together. So good for them and best wishes.

But if you want to be a cynic, you’d speculate that Jon probably didn’t leave Apple just to be the head of engineering execution at a much smaller company. You wonder if the current situation is just a stage in a longer-term changing of the guards at Palm. I don’t have any evidence that’s the case, and I am not trying to start any rumors. But when you see a nonstandard reporting structure like this, it usually triggers speculation that another shoe is going to drop later.

Only time will tell.

What’s the effect on products? That’s the most important question, and it’s impossible to answer at this time. Hardware product development usually takes 18-24 months, so the earliest Jon could change the Palm road map would be very late 2008. But that’s the middle of the Christmas selling season, and you can’t announce products then. So realistically, the Rubinstein product era doesn’t start until spring 2009.

In the meantime, there’s a lot he can do to make the development of the currently-planned products be more efficient and predictable. Palm has said publicly on numerous occasions that its on-time product delivery needs to improve, and presumably Jon can help with that.

But personally, I think Palm’s bigger problem has been its lack of innovative new product designs. Unless Palm has a bunch of surprise products already in development, it will take quite a while to turn around the product road map.

_____________________

Thanks to Twofones for including last week’s post on the Palm Foleo in the latest Carnival of the Mobilists (link).

Wow, what an interesting day this was in the mobile and web world:

–Apple hinted that it will allow third party developers to add applications to the iPhone, potentially overcoming one of the device’s biggest shortcomings (link).

–Google announced Gears, an open source project to enable web apps to work offline — injecting Google into the growing effort to make PC operating systems irrelevant, and linking Google with Adobe (link).

–Livescribe previewed its pen computing device, the latest in a long series of efforts to turn Anoto’s pen sensing technology into a commercially viable product (Livescribe link, Anoto background).

And oh yeah, Palm finally announced Jeff Hawkins’ secret project, the Foleo.

A lot of the online commentary on the Foleo hasn’t been enthusiastic. Engadget called it the “Foolio” (link). Ars Technica’s article was headlined, “Palm officially out of ideas, debuts 1990s palmtop concept” (link). The discussion on the Palm Entrepreneurs Forum (an e-mail list for Palm application developers) was more balanced between admirers and detractors, but even there a lot of people were very lukewarm.

I think a lot of this is Palm’s fault. They’re trying to position the Foleo as a “mobile companion,”* a device that smartphone users can carry with them when they need a keyboard and bigger screen. In other words, it’s for a small subset of the smartphone market, which itself is a small subset of the phone market. A niche inside a niche. The Stowaway keyboard folks should worry.

But I don’t think the Foleo really is a “mobile companion.” Back when I started to work at Palm (before the turn of the century) one of the old veterans of the company pulled me aside and passed along a little wisdom. “Michael,” he told me, “Ya gotta think in terms of real estate. If you’re in another device’s real estate, you’re competing with that device. Palm lives in your pocket; it competes with other things that go in your pocket. If you get bigger than the pocket, you’re living in the briefcase, and you’re competing with the notebook computer.”

Foleo lives in the briefcase. It’s displacing the notebook computer from your bag. I don’t care what they call it, I don’t care if Palm fully realizes it yet, but the fact is that Foleo’s a notebook computer.

More to the point, Foleo is the most significant new consumer PC platform introduced in the US since the Macintosh. All you Linux heads who have been asking for a true consumer Linux PC, you finally got your wish.

Wow. That’s kind of cool. It may be crazy, but it’s a craziness I like. Palm has reimagined the PC for the wireless Internet era, simplifying and stripping away everything they thought was no longer necessary. So since most people carry a phone, you use the phone as your wireless modem. The device also has no hard drive. Since everything is stored in flash RAM, you never actually shut it down — you just turn off the power, and when you turn it on again all your data and apps are still there, waiting for you. This is normal in a handheld, but it’s long overdue in a PC.

“Desktops and laptops were too large, expensive, complex. You’re not going to build billions of these complex machines, you build mobile computers….But it became clear the smartphone wasn’t going to fill that role….You need a full size screen and keyboard.” –Jeff Hawkins, quoted in Engadget

How well will the Foleo sell?

I don’t know. It’s not the product I would have built (my long wait for an info pad continues). The most successful mobile devices in the last decade have been specialized products that solve one problem for one type of customer — iPod plays music for entertainment hounds, GameBoy plays games, BlackBerry does e-mail, Palm Pilot does your calendar, etc. The Foleo flies in the face of that. Although Palm talked a lot about e-mail today, the device also has a browser built in, and clearly has ambitions to be a general-purpose computer. I think we should judge Foleo on those terms, not by measuring it against other products we all imagined or wanted. Here are a couple of quick thoughts, and I’ll probably post more in a few days after I’ve had more time to think about it…

Palm can now succeed even if Treo fails. Palm implied that the Foleo will be able to work with any smartphone, not just the Treo. This potentially gives Palm a larger market, and also sidesteps the operators, since Foleo can be sold through consumer electronics stores. Palm execs have been very public in saying that they are happier selling through retail rather than through operators, so today they must feel a little bit liberated.

Beware the Windows CE factor. I have seen many products very similar to Foleo fail over the years, and that worries me a lot. For years Microsoft and the Windows CE hardware companies produced a series of sub-notebooks that looked eerily like the Foleo. Like Foleo, you were supposed to use them to do light browsing and e-mail. They all died quickly, mostly because they looked so much like Windows that people expected them to run Windows apps. When people didn’t get the full Windows experience, there was an immediate backlash.

Foleo’s a little different because it doesn’t pretend to be any flavor of Windows. But the hardware design looks an awful lot like a Windows PC, and that’s going to create the wrong impression. Maybe Foleo looks nicer in person, but in the photos it looks like an anonymous gray box, disturbingly like a Dell subnotebook. It doesn’t seem to have the lust-inducing look of the Treo 600, let alone the Palm V. I wish they’d made the case more distinctive, or at least a different color, because then people might expect different things from it.

Success probably depends on the apps. Like other PCs, Foleo doesn’t do all that much out of the box. It apparently comes with Documents to Go (a well respected suite of Office apps, ported from Palm OS), an e-mail client, and a browser. That’s all nice, but it’s definitely not enough to make me put down my notebook computer. I think Foleo will eventually live or die based on whether it attracts a lot of third party applications that do interesting things you can’t do with a notebook PC.

Palm has been evangelizing a number of developers to create apps for Foleo, but for some strange reason it excluded them from the Foleo announcement today. Instead, the announcements are going to be dribbled out one by one over the next few weeks and months. I presume the idea was that they’d create a sense of momentum, but I think instead what Palm did is make today’s announcement less impactful than it could have been.

That means we haven’t heard the full Foleo announcement yet. There’s more to come from the third parties. We won’t be able to really judge the device until we see the totality of what it’ll do at launch.

My bottom line, based on what I know today: As a standalone mobile data device, the Foleo is uninspiring. As a potential challenger to the notebook PC, I want to believe, but the proof will be in the third party apps.

_______________

*By the way, the term “mobile companion” is perilously close to “PC Companion,” one of Microsoft’s early terms for Windows CE devices. The phrase gives me hives, but I think that’s just me.

Welcome to the 70th weekly Carnival of the Mobilists. If you’re not familiar with the Carnival, it’s a collection of mobile-related commentary from the last week, nominated by the weblog authors themselves. The hosting duties rotate from week to week.

This week’s articles cover a huge range of subjects, from game-playing cameras to RIM’s service outage. I tried to come up with some clever theme to link them all together, but I think the main message is that the mobile market is so diverse that there are no common themes.

And away we go…

RIM’s service outage: Are they liars, or just incompetent? Wow. The Mobile Enterprise Weblog gives a scathing analysis of RIM’s recent service failure, and concludes:

“Either RIM’s NOC is managed by idiots OR RIM’s PR department is incompetent OR none of the above.”

(With ‘none of the above’ meaning the company had a more serious failure and is trying to cover it up.) I have no idea what really happened, but this commentary is what occurs online when you try to play down a story. It’s far better to be completely open about a problem. Then at least people may trust you in the future rather than assuming you’re lying.

MVNOs: Victory of the bottom-feeders? Jason Devitt at Skydeck, a mysterious new mobile startup, contributes a very interesting post on the fate of MVNOs. He argues that the high-profile MVNOs targeting lucrative customers are doomed, and that the ones to watch are those targeting low-end customers.

How to improve feature phones. Little Springs Design reviews some of the flaws of today’s feature phones, and makes suggestions on what needs to be changed.

American business executives should all use SMS instead of e-mail. That’s the message from Tomi Ahonen’s fervent (and very detailed) essay on the benefits of SMS messaging, and its ubiquity outside the US.

The dumbest convergence product of all time (in my opinion). Pocket Gamer brings us news of a new digital camera that comes with twenty video games built in. They treated the product with very polite respect, but I can’t restrain myself: I thought I had seen dumb convergence products before, but this one’s the new champion.

Using SMS to communicate to students. Mopocket editorializes that universities should use text messaging to communicate with students in emergencies.

The rebirth of Web Clipping? Well, sort of. Web clipping was a technique Palm used several years ago in an effort to overcome the latency problem with accessing web content on mobile devices. David Beers predicts that Palm’s going to use something similar in the future.

Anger over mobile data charges. Helen Keegan editorializes on the charges for mobile data in the UK, and she’s not happy.

Enthusiasm for Nokia’s web tablet. b-trends brings us a very enthusiastic review of the Nokia n800 Internet tablet device. They tested a nice range of websites, and there are good screen shots.

Checking out a new operator in Spain. WAP Review gives a hands-on review of the Spanish operator Yoigo.

The future of mobile advertising. Always-on Real Time Access summarizes a recent panel on mobile advertising.

Future barcodes. The Pondering Primate speculates about possible future competition between Microsoft and Google in barcodes.

Mobile phone myths corrected. Shackkdiesel tackles some interesting myths about mobile phones.

Which devices to target in enterprise? Mobbu talks about the process for choosing which devices to target when creating an enterprise mobile application. It’s not always best to pick the most advanced device.

Bloggus interruptus. My submission for this week is a short commentary on trying to use the mobile Internet while riding on a train.

A robot to load the dishwasher. SharpBrains contributes a summary of the recent Stanford Media X conference, a technology conference featuring Stanford researchers and others. Most of the content wasn’t mobile-related, but it makes interesting reading anyway. Check out the robot that can load a dishwasher.

Post of the week. Each week’s host traditionally picks a favorite post, and mine this week is Mobile Enterprise’s rant on RIM’s service outage. It’s not the longest post of the week, but the analysis made sense to me, and I always enjoy a weblog post with a bit of passion to it.

So it goes. Next week’s Carnival will be at the Silicon Valley Himalayan Expedition. Anyone with a weblog can submit a post to the Carnival. You can use the new online submission form here.

This afternoon I heard from a reporter that Google and Microsoft are now rumored to be interested in buying Palm. I have no idea who starts these rumors, or whether there’s any truth to them, but they’re not nearly creative enough. Here’s my list of other companies that have absolutely no interest in buying Palm, but ought to be in the rumor mill anyway. Feel free to re-use these if you want to manipulate the stock market. No need to credit me; I don’t want to be visited by the Feds.

7. Airbus

Compelling business rationale. I hear Airbus has a lot of trouble with the wiring in the A380, and there’s a bunch of wires and stuff inside a Treo, so this seems like a good match. (Hey, it makes as much sense as Google buying Palm.)

6. eBay

Compelling business rationale. Most Treos end up on eBay eventually, after their owners upgrade to a new model, so this is an opportunity to “significantly integrate the value chain,” as we say in the business. Each Treo could come with an eBay account, enabling the user to offer it for sale whenever they’re ready.

As an added benefit, a Skype client could be bundled with every Treo sold. (By the way, this is apparently the only way to get Skype to port its full native client to Palm OS.)

5. Ben & Jerry’s

Compelling business rationale. What if Jeff Hawkins designed ice cream flavors?

4. Cisco

Compelling business rationale. Apparently not required for a Cisco acquisition.

3. DaimlerChrysler

Compelling business rationale. I propose a straight-up equity swap: Palm for Chrysler. Daimler would give away a company that’s talented at design, but whose products have fallen behind the innovation curve, and that has problems with execution. In exchange, it would get…exactly the same thing. But as a bonus, Daimler could build a Treo and sync cradle into every car it sells. This fits with the whole convergence thing that’s supposedly driving all industrial development in the western world, so this merger is a natural.

2. HP

Compelling business rationale. No, wait, this one actually makes sense. Never mind.

1. JetBlue

Compelling business rationale. Give a Tungsten to every employee, pre-loaded with a datebook alarm that says, “Time for the airplane to leave now.” The acquisition would pay for itself within three months.

I scan a lot of technology weblogs, and it has been fascinating to see how the recent New York Times report on the hiring of Paul Mercer by Palm has been echoed all over the blogosphere. The story seems to have some sort of special iconic importance to a lot of people; they view it as a response to the iPhone, or as a milestone indicating trouble for Palm.

Paul’s a good guy, he had a nice reputation at Apple, but it bewilders me that the Times picked up on that particular hire. There has been a ton of change in Palm’s marketing and product marketing organization in the last year, starting long before the iPhone. Two of the leaders in the team left, and Palm recently hired Brodie Keast to run the whole thing (Brodie is a very senior, longtime veteran of Apple, Tivo, and a bunch of other places). Brodie reorganized marketing, some iconic Palm veterans have left (including Rob Haitani*), and Brodie has brought in some new people. There hasn’t been a peep about any of that on the New York Times, or any blog I read. But Paul’s hiring gets a ton of play.

We’re told that blogs act as a supplement to the mainstream press, digging out the real stories and adding lots of missing detail. But sometimes the press and blogosphere together are just a big echo chamber. In this case, I think everybody has missed the real story, a longer-term changing of the guard at the company. Weird.

________
*That’s what I was told by a Palm employee, but I haven’t seen an official announcement, so please view it as a strong rumor until there’s confirmation.

In case you missed it, there’s a long interview with Jeff Hawkins of Palm over on PalmAddicts. In the interview, Hawkins hints very strongly that he’ll show the company’s new “third category” device in May.

“We’re going to be announcing something…but I won’t tell you what it is…we will be launching this year, not in the distant future. I’ll give you a much bigger hint: I’m going to be speaking at Walt Mossberg’s D Conference in May. It’s a high-end industry conference. Anyway, I’m going to be giving a talk there, and that would be something for the Palm fans to keep a close watch on.”

That should be enough to get the rumor mill cranked up again.

________

By the way, I apologize for the shortage of posts recently. I had the opportunity to work on a couple of papers with Prof. Joel West of San Jose State, discussing the iPhone and some other interesting subjects. They ate into my blogging time. I’ll let you know when the papers are available.

Joel has an interesting blog on open strategies. It’s worth checking out.

A reader sent me a note asking if I had seen the thread on Treo Central discussing some patents Palm received on mobile devices with folding screens. Several people have been speculating online that this design might be the new category of device that Palm’s developing.

The product designs depicted in the patents are intriguing. They show a device that looks like a mobile phone:

…but opens to reveal something that looks, well, almost exactly like I’ve always imagined an info pad would look:

There’s a flexible screen on the inside, so you get one continuous writing or viewing surface when the device is opened.

Alas, the patents tell us almost nothing about what Palm might be developing today. If you look carefully, they were filed in January 2001, when Palm had a completely different senior management team.

Some of the inventors don’t even work at Palm anymore. Frank Canova is mentioned in one of the patents. He was head of advanced technology at the time, but left the company in 2002. Rich Gioscia is on several of the patents. He was driving industrial design at the time, and is still with the company.

The patents can’t be early prototypes of Jeff Hawkins’ secret project, because he was not working at Palm at the time. It is possible that the ideas filed for by Canova and Gioscia and the others were incorporated into Hawkins’ project, but it’s just as possible that the patents represent an old idea that the company abandoned years ago.

This sort of thing often happens with patents — many tech companies pay bonuses to their engineers to file for patents on almost anything they can think of, because patents are used like trading cards in industry negotiations. It’s helpful to have a big collection of them. Even if a patents was for a real product that was being developed at one point, by the time the patent’s granted the company may have changed its plans completely.

But I will say this: I want that folding device so badly that it makes my teeth hurt.