Android operating system has been tremendously successful. It's become
the top selling phone platform in the world and its app store is stocked with
close to 200,000 apps. But for all that success, a perpetual criticism is
a perception that Android's environment is too heterogeneous across various handsets --
part of this is due to carriers/hardware partners failing to roll out the
latest versions, but part of it is due to customizations such as Motorola's
Motoblur and HTC's Sense UI.
I. Bye Bye Open Source -- For Now
Perhaps that's part of why Google has decided why not to release the source
code for Android 3.0 "Honeycomb", yet.
The company states that the code isn't ready yet for external modification,
despite the fact that products are being sold with it installed, today.
Aside from preventing unwanted third-party user interfaces, the chief goal of
the delay is ostensibly from preventing Honeycomb (Android 3.0) from being put
on smartphones. Google is pressuring smartphone makers to instead use Android 2.3 "Gingerbread". Google
is also less-than-enthusiastic about Honeycomb entering other devices, like
set-top boxes and automobiles, without further modification.
Andy Rubin, vice-president for engineering at Google and head of its Android
group essentially admits that the move is being made to prevent the platform
from heading, in its current state, to places Google didn't intend. In a BusinessWeek interview,
he states, "To make our schedule to ship the tablet, we made some
design tradeoffs. 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
He adds, "Android is an open-source project. We have not changed our
Then he makes an even more surprising statement -- he says that if his company
released Android's source, it couldn't prevent phone makers from putting it in
a phone form-factor "and creating a really bad user experience. We have no
idea if it will even work on phones."
That statement is intriguing because it sounds a lot like arguments against open
source operating systems that one of Android's top competitors, Apple, made in
recent years. And while the delay doesn't mean Google has closed its
project off from the public, it does indicate that the company is increasingly
seeing eye to eye with Apple on this issue.
Dave Rosenberg, a longtime executive in the open-source software world,
complains about the decision, but admits, "Everyone expects this level of
complete trust from a company that's worth $185 billion. To me, that is
ridiculous. You have to be realistic and see that Google will do what is in
[its] best interests at all times.
II. What Will the Impact of Google's Newfound Selectiveness Be?
Ultimately this issue will supposedly be washed away with Android 3.5 "Ice
Cream Sandwich", which will unify the smartphone (Gingerbread) and tablet
(Honeycomb) trees into a single operating system.
In the meantime, it's possible Google could make stop-gap modifications to
improve the Honeycomb experience on smart phones, and release a minor update.
Mr. Rubin states, "The team is hard at work looking at what it takes
to get this running on other devices."
It's hard to say how the move will affect sales.
Sales of the Samsung Galaxy Tab were quite good, despite the interface (Android 2.2
Froyo)feeling clunky on a tablet. By contrast the
Motorola Xoom offers a vastly superior UI in Honeycomb, yet has struggled in sales.
Part of this may be due to price -- the Tab debuted at $399 USD on at least one network,
while the Xoom debuted at $799 USD.
The true test of whether the decision to close off the platform should be soon
at hand, though. The Xoom has dropped in price, with a Wi-Fi version launch on Sunday at $599 USD. And Samsung
will soon air a second generation Galaxy Tab 8.9-inch tablet
for $469 USD and a a 10.1-inch variant for $499 USD, rumored to launch on June
8. Dell also looks to soon air updated versions of its "Streak"
Android tablets, at competitive prices.
Despite that the decision to temporarily close the source may benefit Google
and its customers experience, not everyone is happy with it.
Eben Moglen, a professor of Law at Columbia Law School and the founding
director of the Software Freedom Law Center, argues that Google is repeating
the mistakes of industry giants like Apple. He states, "[Closing
your source is] usually a mistake. Long experience teaches people that exposing
the code to the community helps more than it hurts you."
quote: someone can get inside your phone, alter and delete stuff and never ask permission in advance
quote: And Apple can't? You are probably giving them permission to do so just by buying the phone. Remember those bricked after a firmware update?
quote: "Apple and its licensors reserve the right to change, suspend, remove, or disable access to any Services at any time without notice. In no event will Apple be liable for the removal of or disabling of access to any such Services. Apple may also impose limits on the use of or access to certain Services, in any case and without notice or liability."Straight from the EULA.
quote: Seriously, it's hard to know what that refers to? I know you're smarter than that Tony. If not, go read the entire EULA, it's public.I don't have an iPhone, but maybe you can tell me what remote wipe does?
quote: I'm sure if that was in Android's EULA you would be using it to your advantage.Another case of Mr. Swash circumventing around a subject he obviously has little knowledge of. If this trojan had not divulged the remote wipe capabilities on the Android platform, no one would have known about it. Does that mean it wouldn't have existed if this didn't happen?
quote: Again no evidence that Apple can change the code or alter the content of your iPhone without you knowing about it or giving your permission. And no evidence that Apple intends to do so. Remote wiping of stolen iPhones has nothing to do with this.
quote: Don't play dumb. You know that can't be proven since the law prohibits anyone from looking into Apple's code.Remote wiping is proof enough data can be erased remotely, isn't that what you were asking for? When a firmware update bricks your phone, isn't that altering the content of your phone without asking permission?
quote: Should buyers of Android handsets been told that this was something that could happen?
quote: C'mon, Tony. You know as well as I do it's not as black and white as answering just a few simple questions. These are valid questions, however, you know as well as I do that each scenario would need to be assessed individually, with the main focal point being what is the end impact to the user.My point was that if evidence proves existence, does that which has not been evidenced not exist?You're getting into a complicated and very controversial topic. However in this case, as you have already pointed out in one of your previous posts if I recall correctly, Google performed this act of judgement for the good of its consumers.The only one I can answer is this one:quote:Should buyers of Android handsets been told that this was something that could happen?Yes I do believe consumers should be informed.There is no proof to suggest anything otherwise, and until there is, it's hard to answer any of your questions or even determine whether it's right or wong that any company should have the ability to perform these actions.