OS Licensing and Firewalls: That's Not the Point

I see where Andy Rubin said Google is building a "firewall" between the Android team and Motorola Mobility (link).  That's exactly what we called it when Palm licensed out its OS, and actually the firewall worked pretty well.  I'm sure Google can and will prevent information leaks between the Android team and the Motorola team.  Those teams do not work in the same buildings (many of them are not even in the same state), so that's pretty easy to do.

Most PalmOS licensees didn't have big worries about our firewall.  They wanted to know it was in place, and they were careful about sharing information with us, but we were able to work together.  The reality is that if your OS is selling well, the licensees will put up with almost anything (look at the early history of Microsoft if you doubt me).  And if sales slow down, no amount of firewalling will keep them loyal.  Look at the, uh, more recent history of Microsoft in mobile.

The place where Palm had trouble (okay, one of the places) was that it could not figure out what to do when the financial interests of the OS conflicted with the financial interests of the hardware team.  It wasn't about the firewall, it was about the corporate business goals.  To put it in Google terms, what happens when a change to Android will hurt sales at Motorola Mobility?

Let's make up an example: Suppose that Motorola needs a new feature in the OS to support its next-generation product line.  It has already started building the new devices, and has...say, $200 million in parts already ordered to build them.  The orders cannot be canceled, and the parts will become obsolete if not used quickly.  The Android team has trouble implementing the feature, and realizes that it will have to choose between the feature that Motorola needs and another feature that HTC needs for its next-generation products.  It's a zero-sum game; there are only enough engineers to produce one of the features.  Who wins?  Will Google accept a writedown of $200 million to protect its promise to HTC?

This is not a theoretical question; tradeoffs like that happen all the time when you're developing an OS.

Want to guess how those questions were answered when Palm hardware and Palm OS were in the same company?

I think that's the real reason why Palm and PalmSource had to be separated, and I think that's the real question Android licensees are thinking about.  Not is their information safe, but would Larry Page accept a financial bloodbath at Motorola to protect other Android licensees?  If Google has addressed that question, I haven't seen the answer.  It's a very hard question for any CEO because it pits the interests of Android licensees against Google shareholders.

None of this will drive away Android licensees, but I think it will affect the strength of their interest in also working with Microsoft -- which, when it abuses its licensees, tends to abuse all of them equally.

Information Overload: Several Different Problems Under a Single Name

I want to thank everyone who participated in the information management survey that I posted at the start of the year (link).  The survey was long and complex, but more than 400 of you responded to it.  I know you've got a busy life, and it was very nice of you to help.

Your responses helped to shape the work we're doing on Zekira, the new app being developed by the startup I'm working on.  I have posted a summary of the survey findings here (link).  I know you read Mobile Opportunity for tech industry commentary, so I'm going to continue to blog on that subject here (hopefully more frequently).  I will post Zekira-related information at the Zekira weblog.  If you're interested in information management issues, I hope you'll visit us there.

I think some of the survey results will be interesting to folks here, so let me give you a quick summary of the highlights.

In the tech industry, we talk a lot about information overload, but we haven't defined it very well.  What I learned from the survey is that info overload means something slightly different to every person.  It's not a thing, it's a range of problems caused by dealing with more information than you can hold in your head.

For some people the problem is too much e-mail.  For others it's too many meetings.  For still others, the biggest problem is finding a way to access the archive of old files and information they have accumulated over the years.

Some of you -- I guess I should say some of us -- have amassed truly awesome personal archives of information.  Literally terabytes of data in some cases.  Now if only we could get the information back out of them.

A few statistics on information overload:

--More than 40% of the respondents said they feel overwhelmed by the amount of information in their lives.
--About half of the respondents experience information overload several times a week, and about 15% experience it several times a day.
--20% of the respondents receive more than 25,000 e-mails every year.
--A quarter of the respondents receive more than 100 text messages a day.
--A third of the respondents have saved more than 100 gigabytes of business files in their personal archives.

One of the biggest challenges in creating a product to help with information overload is figuring out where to focus it.  Which specific problem(s) do you want to solve?  Which people care about those problems?  And how do you put a dent in those problems with a startup's resources?

In the next few weeks we'll be talking about how we answered those questions.  You can follow our progress at the Zekira weblog.  And you can read more about the survey results here.

And again, many sincere thanks for your help.

We now return you to our regularly scheduled programming.