This is a required step if Google wants the platform to be taken seriously. The only way to keep fragmentation out is to exert a fair amount of control over the OEMs and Carriers who wish to differentiate (or Fragment) Android for their own purposes.
It's going to be a fine balancing act for Rubin. If he pushes the carriers/oems too far, they'll walk. If he doesn't push them hard enough, the platform will disintegrate Java ME style.
Google is using the only leverage they have (early access and the google apps) to make the platform one worth developing for. I, as someone who makes his living doing it right now, am all for this move.
People need to tone down the rhetoric, in my opinion. Android already is being "taken seriously". Let's not make small problems out to be big problems. Android doesn't have any big problems, as it's being adopted by manufacturers and consumers at a rapid pace.
The fact remains that Android's fragmentation is something I deal with on a daily basis. Any time spent fixing issues that crop up on particular phones is time I don't spend adding features to our application. Keeping customers from knowing the joys of fragmentation is one of the things I spend a lot of thought and work at.
Each phone has a different camera app, different gallery, different everything. Its annoying. They're all more or less phoned in - if you pardon the pun.
What google really needs to do is address its ugly stock GUI and put some shiny on there. Put in a decent media player. Put in lots of Apple-quality apps so that OEMs don't feel the need to completely redo everything because the stock android looks like something a defense contractor would make.
Maybe they can even make custom GUI enhancements run in userspace so that updates don't require redoing them. There should be a skinnable layer on top of system widgets. Heck, once you have that then google can start pushing out its own updates to phones and OEMs won't need to wait 8 months to port them over.
One can dream, I guess. Or I can buy an iphone again or move to Win7. My little Android experiment isn't really going anywhere. Its just as locked down as an iphone in practice and I suffer with Samsung's or HTC's low quality enhancements.
I've been amazed each time i've put on cyanogenmod to replace the default android that comes with the phone with how much more useful it gets. Smoother, better working and less lag.
I would love to see htc(or any other hardware maker) ship their phones with a cyanogenmodversion that will track cyanogenmods updates. That might even save them some work.
The source will be released when Google is happy with the product. For people to be up in arms that they aren't releasing the source to an unfinished product is ridiculous. Seems like they are damned if they do, damned it they don't.
The Motorola Xoom is already out.. so how is Honeycomb an unfinished product if it's in consumers' hands? The basic spirit of FOSS is that users and developers should be able to modify the code. The article you linked to says this:
>The lack of Honeycomb code availability is especially bad for enthusiasts who were hoping to be able to install custom firmware on their Android tablets. Without the code, it will be difficult for the modding community to produce custom builds that fix the software problems that plague the Xoom and other upcoming Android tablets. Users who were looking forward to better Honeycomb builds for the Nook Color and other budget devices are also going to have to wait.
>For now, only a privileged few hardware vendors will have access to Honeycomb while the rest are left with uncertainty about the future of the platform. Even after the matter is resolved, the fact that Google is willing to withhold source code at its whim for competitive reasons is going to continue to cast a dark shadow over the company's increasingly hollow claim that Android is an open platform.
I don't see how the above is wrong.
>The source will be released when Google is happy with the product.
Doesn't Android use the Linux kernel which is GPL'ed (among other parts)? Can they legally withhold code for a shipping product by saying the software isn't finished?
That they're allegedly holding up Android phones which utilize a rival search engine, Bing, is especially troubling. Is Android supposed to be an open platform or a Google platform?
Walking isn't such a big issue these days. Which is likely why Google feels secure doing this. Windows CE is dead. Phone 7 is struggling. Nokia essentially gave up, removing MeeGo as a concern.
So where does, say, HTC go if Google pushes them to drop the Sense UI?
They certainly don't have the software expertise to fork and run. None of the Android OEMs do. At the rate mobile is advancing, they'd be irrelevant in 18 months. And there is literally no-one else who is delivering a product they can use to maintain their sales.
I honestly wonder if Google isn't more concerned about Amazon than the OEMs.
As for carriers... they're only a real issue in the US; where Android's growth isn't that strong anyway. I mean, is it even possible for AT&T and Verizon to support Android less these days? I haven't seen a single Droid ad since January.
Others like Motorola and Samsung, I'd expect them to stick to Android whatever happens, at least for the high end. This is why Google is doing this.
/semi-sarcasm.
Can we finally stop saying Android is 'open' now when it's blatantly false?
Imagine the headline read 'Apple Tightening Control of WebKit'. How is this any different?
I truly want to see an Open tablet on which the community could realize the Dynabook vision. I thought the Xoom might be a good starting point but with Google capriciously exercising power over the software, it's pretty clear that Android isn't going to give us that.
On the bright side, Moore's law will give us tablets that will run stock Linux pretty soon, and then all we need is a BSD-licensed, community built touch layer.
Could you explain how Moore's Law is relevant here? How you get from "Number of transistors per IC will double in 18 months" to "Linux on a tablet pretty soon"? Tablet development isn't being limited by processing power as far as I know.
Most people I know who have an iPad 1 complain that speed is an issue. The iPad 2 certainly fixes that, but Apple's have focussed a lot on optimization and their stack is all built around compiled code.
To me that suggests that tablet performance is only just adequate today.
If we want to realize the dream of a truly open, programmable-on-the-device tablet, we're going to need it to burn some cycles on languages that aren't as efficient as C, and frameworks that haven't been as tuned as iOS.
Why did you use this example? Apple isn't tightening control of WebKit. WebKit is a considerably more open project than Android.
Can you assuming that you have C skills tell Linus that we all should use a new file system called FUD? NO! Is Linux any less open because you cannot ? NO!
please effing stop with the damn fud
The only people this limits "openness" for is device manufactures, which most developers would probably consider a good thing.
And as a user - you can still buy handsets that allow you to use Amazon appstore or side load apps. So yeah in the spirit of everything being relative - it is still far more open - just enough to be not a detriment.
Facebook, for example, has been working to fashion its own variant of Android for smartphones. Executives at the social network are unhappy that Google gets to review Facebook's tweaks to Android, say two people who weren't comfortable being named talking about the business. Google has also tried to hold up the release of Verizon (VZ) Android devices that make use of Microsoft's (MSFT) rival Bing search engine, according to two people familiar with the discussions.
With Google being direct competitors with Facebook and Microsoft in the online space, they have a lot to gain by knowing their competitor's plans early/by being able to limit their influence.
If I were Facebook, I'd just avoid Google entirely and use alternative apps for everything. Amazon Appstore, Facebook Messaging for email, etc.
The source to Android is made public at or around the time the final version ships but until that point only select partners have access to the software. It's this approach that Google are going to strengthen - essentially if you don't obey their rules you won't be a select partner and you won't get early access to the new releases.
What this means is that if you don't obey Google's rules you'll be getting the software two or three months later than your competitors (and without all the support they will be getting), likely receiving it around the time they're actually bringing products to market. That's a pretty big competitive disadvantage if you're aiming to compete at anything close to the top end of the market.
So basically while you can use Android as you wish, if you don't obey Google's rules then you won't be able to do so in a way that allows you to be competitive.
The cynic in me says that this is getting mighty close to being open in name only.
How much of a big deal this is would depend on what market segment they're going after, but mapping and location services are awfully handy across the board, and available on pretty cheap phones at this point.
Maybe Google didn't really have the clout to exercise control until now, but I'm really glad it's finally happening.
What I hope this means is that Google will control everything on the OS level, and allow customizations by the manufacturers and carriers only on a skinning and app level. In a perfect world they would also enforce access to bootloaders, to allow easy rom changes.
The thing that irritates me is the considerable double standard for freedom and openness that is applied to Android and iOS. As it turns out people have an very relative concept of what 'free' and 'more free' is. Some types of freedom are considered good, while others are bad. Hard to tell at times which way the community will go. I come in to these kinds of stories and find people endlessly lauding Google for taking more control over the ecosystem. I know for a fact that if the story were 'Apple cracks down on X' the reaction would be practically the inverse.
I am inclined to believe Nokia went with Microsoft primarily because Microsoft needs Nokia more than Google needs Nokia, i.e. Microsoft offered more money.
But I guess with the new Amazon market the old Google carrot/stick is no longer as compelling.
http://www.businessweek.com/magazine/content/11_15/b42230412...
tl;dr version - Google is allegedly asserting greater control over what folks who ship Android can do (presumably as part of the license for the Google apps bit). They are uneven in their enforcement.
Often times articles like this have some base message or meme they are channeling but this one doesn't seem to have much focus. One would guess it was this bold claim:
"There will be no more willy-nilly tweaks to the software. No more partnerships formed outside of Google's purview. From now on, companies hoping to receive early access to Google's most up-to-date software will need approval of their plans. And they will seek that approval from Andy Rubin, the head of Google's Android group."
But its not really backed up by the story line. The story is more a "they are lying about openness, they are really evil" kind of thing that I've noticed quite a few places are picking up. There is insinuations about the justice department and anti-trust. Frankly it reads like something Microsoft would say.
That being said, if Microsoft really is behind articles of this tone, then I'd suggest they take a different approach and offer carriers a replacement for the Google apps package (mail, maps, search, chat etc) and create windows mobile/android that would certainly tweek Google's nose.
Suppose google doesnt approve changes to the source code before the companies release products. Suppose the changes to that source code stop certain apps from working on certain phones, therefore putting it on the shoulders of the developers to make certain their app works on every different phone.
It would hurt the quality of the apps and the platform if Android lost its mostly seamless cross platform ability
Haha, oops! That is kind of funny. I can't believe Google didn't anticipate this type of thing.
