Slashdot Mirror


The Shortcomings of Google's Open Handset Alliance

eldavojohn writes "Former T-Mobile and Apple executive Leslie Grandy reports some pretty harsh words about Google's Open Handset Alliance. We've heard grumblings before about control in open source projects, but now an unnamed former leader of an OHA member company is calling the OHA 'oligarchical,' and said, 'The power is concentrated with the Google employees who manage the open source project. The Open Handset Alliance is another myth. Since Google managed to attract sufficient industry interest in 2008, the OHA is simply a set of signatures with membership serving only as a VIP Club badge.' But what privileges do they have? Not many. The OHA's problems don't stop there; Grandy maintains that 'many OHA members are developing proprietary user experiences, which they are not contributing back into Android — as is standard for open source projects — for fear of losing competitive advantage in the marketplace.' She goes on to paint the OHA as toothless and directionless, with a nearly abandoned message board. It's been around for almost three years, and while Android has become more prevalent, the OHA's contributions seemingly have not. Do you agree that the OHA has amounted to nothing but a checkbox for manufacturers?"

14 of 208 comments (clear)

  1. Not a checkbox, a shortcut... by nweaver · · Score: 4, Interesting

    Its not a checkbox, but rather a shortcut.

    If you are making a smartphone, you need a powerful OS, with a lot of low level features, and as robust as possible an app market.

    And if your name isn't Apple or RIM, you need an off-the-shelf OS from someone else. WinCE (or whatever Microsoft calls it this week) doesn't have the app ecology and costs money to put on a phone. So you go with Android.

    So its not a checkbox, but rather a necessary shortcut, if you want to bring a smartphone to market, you run Android. But at the same time, of course you customize it: you don't want to be a commodity vendor.

    After all, whats the difference between Dell and HP? Not much. HTC doesn't want to be the same as motorola, so in order to preserve a competitive advantage, you try to make your GUI better AND don't feedback your gui changes back to your competition.

    --
    Test your net with Netalyzr
  2. What did you expect? by MadKatAlpha · · Score: 3, Insightful

    Did anyone really expect the OHA to be a real collaborative effort? By getting the big names on the OHA list you bolster OEM and consumer confidence in Google's platform. It doesn't really matter if the members of the OHA have not made any meaningful contributions other than their names. The names were enough to get the product out and get people using it.

  3. Not Familiar with OHA... by BJ_Covert_Action · · Score: 5, Insightful

    I am not familiar with OHA at all, but doesn't it seem like someone who once worked as the CEO of two of Google's competitors might just be biased a little bit? I guess what I am asking is why should I take Grandy to be anything other than an astroturfing shill?

  4. Whiner by buback · · Score: 3, Insightful

    So google is doing all the contributing, but they have undue power over the direction of the platform?

    Shouldn't those that contribute have the most influence?

    If they want to take the OS in a different direction, why don't they just write the code themselves and fork?

    Oh, right. Because it's easier to whine and complain than to actually write good code.

  5. Created with no power. by pavon · · Score: 3, Interesting

    Google's Android specific code is released under an Apache license which has no restriction on creating proprietary derivative works. Members of the OHA were not required to commit to releasing open handsets, and in fact some mobile companies are already planning on shipping versions of Android that will only run signed code purchased from their app store.

    This is what happens when you don't demand reciprocal behavior in your contracts and licensing - the freedom you give to others will be used to restrict the freedom of end users and third parties.

  6. Differnt phones for different folks by brunes69 · · Score: 4, Insightful

    many OHA members are developing proprietary user experiences, which they are not contributing back into Android

    So you are saying that every smartphone in the market will not have the exact same UI?

    Say it ain't so!

    Why does a teenager who is concerned with facebook and twitter have to necessarily want the same user experience as the corperate employee who is more worried about Outlook sync and calendering?

    Having a diverse platform ecology, while still maintaining a consistant underlying architecture to enable a vast application ecosystem, is the main strength of the Android platform (especially compared to the iPhone or Windows Mobile), it is not a weakness.

    1. Re:Differnt phones for different folks by ircmaxell · · Score: 3, Insightful

      Yes, but Google has already committed to fixing those shortcomings in FroYo (at least that's the implied release timeframe). Basically, they are going to uncouple everything from the core OS they can, and provide updates through the market just like for apps. So then it would do dependency tracking. So even though your phone is using an older "core" OS, it can update many of its libraries and "core" applications without the need for a full ROM.

      There's really a fine line between the major player's stances on open source...:

      Apple: Proprietary and Open Source can live together! Just as long as the Open Source is in our interests!

      Google: Proprietary and Open Source can live together! Just as long as the Proprietary is in our interests!

      RIM: Proprietary is where the money is, so we don't really care about Open Source at all...

      Palm: I'm still here guys, don't forget about me!

      --
      If a man isn't willing to take some risk for his opinions, either his opinions are no good or he's no good
  7. Re:HW support is crucial. by IamTheRealMike · · Score: 4, Informative

    Well, the original iPhone runs the same OS number but that doesn't mean they have the same abilities. The 3GS is capable of quite a few things the original iPhones just aren't and that leads to fragmentation as well, just not visible through the version number. Look at multi-tasking for the most obvious example of this.

  8. Re:HW support is crucial. by RyuuzakiTetsuya · · Score: 4, Informative

    Sadly, iPhone OS 4 isn't supporting the 2G EDGE only model.

    The fact is though. The HTC Dream/T-Mobile G1 was one of the first mass market Android devices out there, released a few months after the iPhone 3G and it's not getting 2.xx goodness, yet the iPhone 3G is.

    --
    Non impediti ratione cogitationus.
  9. Simple Question... by 16K+Ram+Pack · · Score: 5, Insightful

    ... how many shares does she still own in Apple?

    That article reads like pure FUD to me.

  10. Innuendo by ArtDent · · Score: 4, Informative

    Ugh. Both articles are pure innuendo. For example:

    Technical Glitches

    The biggest challenge for Google may be to improve its software and ensure that it can adapt to the mobile market, said Maribel Lopez, an analyst at Lopez Research LLC in San Francisco. Google is on its fourth revision of Android in the past year, in part because of software glitches and missing features, she said.

    Golly! Missing features and glitches...that sounds really bad! But wait, aren't all new revisions of software always to add new features and fix bugs? Seriously, in the four revisions over the last year, Android has far surpassed the firmly established competition in just about every respect. I don't know if I've ever seen such a rate of innovation in a platform before.

    Thought they're written to sound alarming, there's nothing surprising about anything in either of these articles. We already knew that Google's doing all the development in the core platform, so why should we be concerned that they are the ones making the decisions about its direction? We already knew that Android is designed and licensed to allow pieces of the system to be replaced by OEMs and users, so why should we be concerned that they're doing that?

  11. Shocking! by ClosedSource · · Score: 3, Insightful

    You mean supporting phones from four different makers costs more than supporting one?

  12. The problem you describe has been solved by mjwx · · Score: 3, Insightful

    Wow, its amazing the PC industry hasn't collapsed under the weight of all this testing, I mean with so many versions of Windows, .net, DirectX, Java. I mean it's so fragmented. Then you have the hardware.

    All these problems have been solved on the PC, now they just need to make the transition to Android. How does MS, Adobe, Blizzard, ECT... ensure that their software works on multiple platforms. Beta testing, various other testing tools. You know that you can run any version of Android on a VM, it's in the SDK, simple applications can be tested in that fashion, only the complex applications have the issue you describe. Many of the applications I use on my Motorola Milestone have not been updated since the HTC Dream was the only game in town and they still work, some get updated on a near weekly basis.

    Android is new, we are waiting for the tools to catch up. Soon the costs chances of getting a random rejection from the Apple app store will be higher then developing for Android. Fortunately, most of the companies jumping into the mobile development space are simply doing it because it is the Latest Cool Thing(TM) and havent put too much thought into it, thus they wont survive.

    --
    Calling someone a "hater" only means you can not rationally rebut their argument.
  13. Re:HW support is crucial. by mjwx · · Score: 3, Interesting

    Right, but what average user is going to potentially brick their phone for what should be a vendor supplied patch? Rooting/Jailbreaking a device? Sure. A real OS update? No.

    Right, because no-one jailbreaks an Iphone because of the risk it might brick their device.

    Installing a custom ROM is easier then Jailbreaking, the SPL does all the work for you. Rooting is the hard part but generally someone uninformed will pay someone else to do it. Also neither rooting nor replacing the OS can brick an Android device, seeing as the boot loader is completely separated from the OS, if the OS upgrade goes bad you don't brick the whole phone, you just re-install the standard ROM (Both HTC and Motorola have them on their web site). To brick an Android device you need to break the boot loader from inside the OS, then break the OS and after all that you can still recover the whole thing using the tools in the SDK (Fastboot IIRC)

    So after correcting your erroneous information about Android and people in general, your point is moot, 2.1 is available for the HTC Dream and Magic.

    --
    Calling someone a "hater" only means you can not rationally rebut their argument.