Google to delay Android ‘Honeycomb’ distribution; can’t run on phones

“Google says it will delay the distribution of its newest Android source code, dubbed Honeycomb, at least for the foreseeable future. The search giant says the software, which is tailored specifically for tablet computers that compete against Apple’s iPad, is not yet ready to be altered by outside programmers and customized for other devices, such as phones,” Ashlee Vance and Brad Stone report for Businessweek.

“In the past, Google has given device makers early access to versions of Android so they could work on their products,” Vance and Stone report. “It would then typically release the source code to the masses a few months later, letting all comers do what they want with the code.”

MacDailyNews Take: Fragmandroid.

Vance and Stone report, “It’s the throngs of smaller hardware makers and software developers that will now have to wait for the software. The delay will probably be several months. ‘To make our schedule to ship the tablet, we made some design tradeoffs,’ says Andy Rubin, vice-president for engineering at Google and head of its Android group. ‘We didn’t want to think about what it would take for the same software to run on phones. It would have required a lot of additional resources and extended our schedule beyond what we thought was reasonable. So we took a shortcut.'”

MacDailyNews Take: So, who’s going to line up around the block for pretend iPads running an OS that features design tradeoffs and shortcuts?

Read more in the full article here.

MacDailyNews Take: Apple doesn’t take shortcuts.

[Thanks to MacDailyNews Readers “Fred Mertz” and “chew” for the heads up.]

34 Comments

  1. Did you see Steve Jobs’ keynote when he presented the iPad 2 to the world at the Yerba Buena center a couple of weeks ago.

    There was a telling statistic that he flashed up in the big screen. That was the number of apps developed for the respective tablet platforms.

    First he showed the number of apps developed specifically for the iPad available on the iTunes App Store: 65,000. 

    Then he flashed a bee logo up onscreen with the number of apps at 00,0100. 

    That tells you right there why Google had to withhold the Honeycomb source code. Not only is the number of apps developed for Honeycomb a pathetic 100, the number of apps capable of running on Honeycomb phones would approximate to the number of brain cells in Eric Schmidt’s brain: 4.

    1. Well, not quite. I’m an Apple cheerleader as much as the next MDN reader, but what you said is not exactly correct.

      The number of Android apps Jobs referred to was for those that were FORMATTED to specifically work on a TABLET device; not necessarily specifically for Honeycomb.

      When Honeycomb does come out on a phone, it is more than likely that not all 200,000 (or whatever) Android apps will work on it, but significantly more than 100 or so definitely will work fine.

  2. If a shortcut takes longer, it’s not really a shortcut.

    What google did was get off the trail and get lost in the woods. Now they think that since they found an old set of rail road tracks all they have to do is follow them back to civilization.

    Best of lick to them.

  3. Total failure Google. Total failure. Stop coasting on Linux and Java so much and add some REAL tech to the party. Do some REAL programming on your own. FYI projects with no income and where you are sued by Oracle for Java will likely end up being delayed INDEFINITELY.

  4. it does not even run well on the xoom, which is why moto is going the browser base route ( which the disingenuous call web os).

    Bet you samsung delays their launch even further.

  5. Even though Eric Schmidt was in on details early on Apple’s Board of Directors, Google over 4-5 years later is STILL behind.

    That does not make Google look competent in any way on Android development.

    1. Well, it is not like the Apple board of directors is made up of engineers who design and develop iPad; they don’t really get to see much of details that go into the design and development.

  6. I think Google’s explanation is partial b.s.

    people are taking android and changing it like OMS in China which does not run Google services like search or android apps (OMS runs a few hundred private apps). So Google makes nothing. Google wants to stop this hijacking of it’s OS (so much for openness). As China is one of the biggest growth zones of Android if you minus things like OMS (which is counted in Android market share) Android isn’t making as much for google as droideks think.

    google made about a billion bucks on all non PC platforms last YEAR (about half of that actually from Apple iOS) so it’s not making a lot from Android (in comparison Apple made $10.47 billion from iPhone alone last QUARTER before apps, iAds etc). Apple will make 50 billion or more from mobile a year.

    I think Google wants to protect it’s intellectual property before it loses money doing Android (that one billion a year counts all mobile ad revenues etc before expenses. google spent $700 m just buying ad mob and hundreds of millions on r&d).

    Google doesn’t care about fragmentation (as long as the devices run its ads) but it DOES care when fragmentation stops it from making money.

    weird that if you read droideks comments they all say they are willing to suffer android’s problems like malware, lack of finish, bugs, no carrier updates etc vs iOS because they are supporting ‘open’. Dudes google is interested in making Ad Money – end of story. lol.

    1. Hmm, an astute observation – Google would be fools if they weren’t concerned about their work being used against them, so strategically withholding their code would make a lot of business sense.

      It seems more and more clear to me that Google’s “openness” is mostly posturing, which they use to claim the moral high ground (particularly among the hardcore open-source crowd), while at the same time thumbing their noses at the GPL, and otherwise doing whatever they think the can get away with.

  7. I think the most telling quote of all is this:

    “We didn’t want to think about what it would take for the same software to run on phones.”

    Correct me if I’m wrong, but isn’t that just another way of saying “We didn’t want to think think about what it would take to stop further fragmentation”? So there you go, FanDroids! It’s getting so bad that they don’t even WANT to think about it! Hahahahahaha!!!!!

    1. You’re being too kind… I have an employee with a Droid Uncredible and his flaming mess of a phone won’t stop sending me spam! I have even threatened to fire him (half-jokingly, of course) if he can’t fix his malware-infested p.o.s., but he can’t seem to figure it out. Screw you, Google, for making my life harder for no damn good reason but to say: “We’re open! (to viruses)”.
      /end rant

  8. Developing and operating system is not the same as developing a search engine or an application.

    What these idiots don’t understand is that you have to have TWO [“different”] versions of the operating system, one for what people calls tablets and one for what people calls mobile phones, if the hardware is not the same. Even if only targeting mobile smart phones, will your only one version of the operating system run in all those smart phones? To put simple so that you can understand, only if they have the same processor architecture.

    In reallity you develop the OPERATING SYSTEM for the specific processor architecture/hardware platform; that’s why it is called operating system. If a tablet and phone have the same processor architecture, then the same source code of the operating system may run in these two “different” devices; and this is what Apple has done for, pay attention, the iPod touch, the iPhone, and the iPad. Yes, Apple has come long ways to have the same or very similar hardware architecture in these three mobile devices, so that operating system developers can work on only one version of the source code that is iOS. Yes, and even so, Apple may have two separate source code one for iPhone, iPod touch, and one for iPad, OR it creates two separate images of iOS out of the same source at the time of building it, one built for iPod touch, iPhone, one built for iPad. Have you noticed that when updating iOS through iTunes, the updates are separate for iPod touch and iPad? You bet.

    The fact that iOS user interface look and feel is identical for these three different mobile devices does not mean it is only one version of the source code.

    That’s what those at google don’t get. Good luck trying to run the same source code (whether taken from fragmentoid or honey crumb) of the operating system in all those different mobile phones’ hardware.

  9. Those poor deluded Droidtards must be seething. Open Android Honeycomb is totally closed for the foreseeable future. I’m getting a huge belly laugh. My avatar is laughing at all the pathetic Droidtard fanbois. All those Honeycomb tablets are going down

    1. You must be joking, to say the least.
      The big “open” is not about the OS source, how many people are going to modify the OS, really?
      The real “open” is about being able to compose my own apps.
      And distribute them, all for free.
      Or I can make them in Flash for even greater simplicity and portability.
      How is Flash running on your iPad? Oh right, that might make your EtchaSketch useful without micropayments to Apple, so never gonna happen…
      To be honest, I do not understand why on Android I cant easily access the file system and run standard Linux apps. So I am going to buy an EEE MT.
      Good day.

Reader Feedback

This site uses Akismet to reduce spam. Learn how your comment data is processed.