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?"
Google is FAR MORE CONTROLLING than Apple and android is a less open platform than the iPhone.
Think Different.
Think Better.
Think Apple!
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
I love my work Droid- best work phone I've had, but fragmentation really is a problem with the Android eosystem. To show my point check out this site. Now I realize this is an Apple-fansite, but the numbers quoted are from GOOGLE's Admob. One of the smart things Apple has done is make sure old HW is supported. An original EDGE iPhone for instance, runs the same version as the iPad or 3GS. Fragmentation not only affects the user experience, but it makes things a lot harder for developers too.
First Steve, now Leslie - OHA is still a hundred times better than anything Apple has come along with - at least for users.
Also all the article does is spread FUD about Android.
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.
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?
Motorcycles, Robots, Space Gossip and More!
but isnt the Android UI just an APX application that can be closed source from the rest of the OS(why Helix and other UIs exist in the marketplace).
So Apple's main complaint against OHA is that its mostly proprietary?
This is kind of like Steve Job's open letter about flash where he warns that Adobe could make it proprietary at any time.
Meanwhile no apps can be accepted at the App Store if they even mention Google...
Mr. Pot meat Mr. Kettle
At least google doesnt send private 'representatives' to ask permission to 'search' people's homes http://www.wired.com/threatlevel/2010/04/dude-apple/
Google also doesn't make phone hardware. If someone had left one of Google's servers at a bar and a story about it appeared on Gizmodo, I wouldn't doubt that Google would show up asking a few questions.
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.
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.
If they're asking, it's not fascism.
How about we at least pretend that words like fascist continue to have meanings beyond "someone I don't like and want to call a name."
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.
At least google doesnt send private 'representatives' to ask permission to 'search' people's homes
Why should they search your home? They already know more about you than your mother does. Or have you not been paying attention to the information Google has been gathering at a dramatic rate?
Hello Godwin's Law!
1331461 is only semiprime *sigh* Alas - I am just short of 1337.
... how many shares does she still own in Apple?
That article reads like pure FUD to me.
I can easily install the HTC look and feel on the Nexus One and can use the original Android 2.1 on HTC Desire too.
So, what "not sharing the UI" ?
I know about OMA though.
Quite honestly, Android needs to be -far- more open to end users. For example, take a look at the Motorola BackFlip. It has an interesting hardware design, runs on AT&T, is pretty cheap on contract, but fails in a few main areas.
A) Uses Yahoo search.
Ok, if you want to make Yahoo the default and get a few bucks, fine. But let me change it to Google or whatever I want. Really, I think Yahoo is a crap search engine. I don't want it on my phone. I prefer Google to Yahoo/Ask/Bing/Live/AltaVista/whatever.
B) Doesn't let you use non-market apps by default
If I want to use non-market apps I should be able to without having to download the SDK and load them on that way.
C) Has crap software.
If you are going to ship a phone, computer, etc. use the most recent OS version. Android 2.1 has -many- advantages over 1.5 and many say it runs -faster- than 1.5. This isn't like Vista, this is a true upgrade. Don't screw customers by offering the equivalent of Windows 98 in 2010.
Google should make their software and require members of the Open Handset Alliance friendly to OSS developers and power-users. Let us change the OS, let us install what we want, etc. Perhaps make it kind of hard, but just let us do what we want with our devices and in exchange Android will get multitudes of innovation, new applications, and more marketshare.
Taxation is legalized theft, no more, no less.
Ugh. Both articles are pure innuendo. For example:
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?
You mean supporting phones from four different makers costs more than supporting one?
While your point is valid, I'm not sure T-Mobile really counts as a competitor? They're a Google partner, last I checked?
-Daniel
By this summer you'll have to support the 1G, 2G and 3G versions of the iPod touch, the 1G, 2G and 3G iPhones, the 3G iPhone with more RAM and a faster processor, and the 4G iPhone with both more RAM and a higher resolution. Oh, and the iPad of course.
The biggest new challenge is the higher resolution - some say this will be 960x640 (i.e 2x the current resolution hor/ver), which is imho unlikely as this would be the first use of such a LCD resolution ever.
To me this doesn't sound simpler than the Android fragmentation, at least with Android the market lets you know which apps you can install, with the Appstore you might only get "oh, don't install this on an iPod touch, it won't work".
I would be more interested in articles comparing the wave of 100$/100euro Android tablets which will arrive this summer..
I've been looking at getting a smartphone for a while - and Android is a pretty appealing option - but one of the things that's holding me up is that as far as I can tell, to access all the handset's functionality, I have to be a Google customer. Which I am - I've had an @gmail.com email address since the days when one had to get an invite to get one - and have very few issues with my benevolent overlord. But - unless I'm wrong - the freedom with Android is the freedom to be a google customer isn't it?
Yeah, I suppose so. I was kinda thinking along the lines of T-mobile marketing phones that compete openly with Google phones. But since they don't develop those phones themselves, that's really just the effects of late afternoon - coffee hitting my brain. Ah well...
Still, the history at Apple rankles my nose.
Motorcycles, Robots, Space Gossip and More!
Meego is the obvious choice apart from Android. Only think is... Intel seem to be focused on netbooks, and Nokia can't seem to support their hardware for more than a couple of months.
In particular, Nokia's N900 came with Maemo, which was largely incomplete (the front camera driver is very noisy, for instance, the GPS is slow, FM transmitter is underpowered so much that it doesn't work, portrait mode is largely unavailable and buggy, navigation isn't turn-by-turn, doesn't sync to PC, etc.) An upgrade to Maemo 6 was supposed to be coming, but this is now Meego, except that last Nokia said, they're counting on the community to do their support for N900 for them. This is their flagship product and they're trying to attract open source developers based on that kind of support? Don't they realise that open source developers are used to having hardware support for much longer than windows support periods? Who is going to develop for a platform that routinely doesn't even last a few months before it's abandoned?
Also, Intel and Nokia are claiming they want to do this Meego development all out in the open. But they seem to want to develop the source code only in the open, and then roll their own very different distros, with their own branding, including separate app stores, which is pretty much insane. That said, I'd welcome a nokia app store, since intel's app store for Moblin required credit card details just to browse it. Also insane.
I'm interested to see how this plays out. But really, I suspect Nokia will need to produce a properly supported Meego 1.x (and maybe even 2.x) on N900 if Meego is to have any chance of competing with the already established Android. Otherwise, a lot of N900 owners will probably do what they're already trying to do: replace Maemo/Meego with Android.
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.
Hmm... differing goals, fragmentation, uncooperative parties...
So, it's pretty much like any other open source project, then?
I do love Android and OSS, but you gotta take the good with the bad. In the end, it's worth it.
Android seems like a mess, but one that could be solved. Let's just hope that happens sooner rather than later.
Also what is the static with Chrome OS? It seems like Google is going to way of Microsoft, half develop multiple OSes that later you end up combining into one large cluster muck we call Windows Mobile or whatever it is this week.
As for choice, there is just too much choice in this market... Java might not have been well executed, but really, a runtime (flash, java, silverlight, etc) seems like one solution to tie together all these separate platforms (yet not ideal at all). Android, Bada, Blackberry OS, Chrome, iPhone OS, Mameo, Symbian, Windows Mobile... I'm sure I'm leaving out many....
Does the industry really need this many players? Like any free market I'm sure it will correct itself, but it's just annoying for users in the meantime.
How does this contrast to major desktop OSes in their infancy? It really seems like in the end there will be just a couple market dominators, and the rest will be very niche, like say Linux on the desktop is, a nonstarter for 15 years and running. Just saying.
For the record, I use an iPhone (work issued) have an NexusOne (Don't use it, but sort of liked it, maybe I'll switch at some point) and my personal device is a Blackberry - I use UMA a lot, and enjoy the battery life etc.
Of course. Why wouldn't it? I mean, when you write a webpage, it costs more to support a Windows PC running nVidia as well as a Windows PC running ATI... right?
It's called abstraction, my friend.
The thing with Android being open, will mean interconnectedness, and programmability on a large scale.
Let's say 3 companies have 20 types of android phones in total.
15 of those phones have GPS, frontcam, compass, radio and wireless. Even though the companies differ, the same API can be used to access the GPS, wireless, frontcamera, and so on, each manufacturer has connected their hardware to the same API, so programmers will benefit from a unified base they don't have to worry about.
That's really the beauty of having an open source OS for the phones, developers know what to expect, and manufacturers just have to connect to the proper APIs.
The fact that manufacturers will on some level develop themselves software advantages for their phones isn't really relevant, that's just something they can do themselves and copyright will protect them from others directly copying them.
If however manufacturers don't open their hardware to the APIs so that developers can develop for the phone.. then you have a problem.
This sadly is happening with Samsung and its symbian partnership, a lot of the hardware in samsung phones isn't connected to the API for symbian developers to take advantage of it, and there's regrettably a perceived utter lack of action on their part to open things up to make it easier for symbians developers to implement things for both Nokia and Samsung phones.
Symbian could be doing the same thing as android, it's a stable platform with a lot of hardware behind it, but manufacturers really have to make sure that developers can get to the hardware, otherwise you're not really benefitting yourself or your customers.
Can someone explain why, for example, the HTC Desire has strong (alas, not strong enough) protection against being rooted if it's supposed to be open? Why not just sell the phones locked to a network/OS etc but make no effort to prevent modification. I can understand the arguments for companies like Nintendo, Microsoft etc doing this sort of thing, as it's part of their business model. But why do Google care which ROM I put on my phone; which apps I install; whether I install them to SD card or not? Is the effort locking it down, and the potential lost sales of this phone against another, more easily rootable phone, worth it?
Can't help you there chap. As I said, I am not terribly familiar with the smartphone world at all...
Motorcycles, Robots, Space Gossip and More!
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.'
Whether or not developments are contributed back to the project depends on the license. The BSD style licenses, for instance, have no such requirement.
"I believe in standards, so let's use mine" seems to be the call from Google here.
Rather than accepting that there are whole eco-systems of standards development in which everybody plays according to a set of groundrules, Google's attitude refelcts a continued pomposity that they are better than anyone else and if you don't agree, tough shit, we'll do it anyway.
Evolution theory should teach them that it's not about the survival of the fittest or strongest - but survival of the most adaptable.
If they really wanted to achieve the objective of their gamed and controlled Open Handset Alliance, they would have brought their issues and work to an existing forum, consortium and standards body: they would risk not being able to control the outcome; but gain a wealth of input and fresh ideas from the community - that is surely the real spirit in which Open Source initiatives flourish.
. So, Google - do you support open standards or do just want to get your own way the whole time?