Live data from Hacker News

Google is defragging Android

arstechnica.com

11–20 of 221 posts

Re: Google is defragging Android

#11

It's worth noting how closely Android's apparent path going forward mirror's Apple's strategy with both OS X and iOS: closed end-user components built on top of an open source core. I guess Google's realized that "openness" isn't a meaningful market differentiator for the average consumer.

And we have to assume that Google will do exactly the same thing with Chrome and Chrome OS when it is to their advantage to do so.

Re: Google is defragging Android

#12

Notably, Play services is totally closed. So Google has abandoned the open source part of Android and is now developing the operating system as a completely closed product. Edit: downvotes don't change the truth of the observation. Android is no longer meaningfully open, other than a years old core of basic functions. Just like OSX and Darwin.

"So Google has abandoned the open source part of Android and is now developing the operating system as a completely closed product."

Not sure what's new here.. Play always came with strings attached. OEMs can choose Play or use AOSP and roll their own Play analogue like Meizu or Xiaomi or Amazon.

Re: Google is defragging Android

#14

Notably, Play services is totally closed. So Google has abandoned the open source part of Android and is now developing the operating system as a completely closed product. Edit: downvotes don't change the truth of the observation. Android is no longer meaningfully open, other than a years old core of basic functions. Just like OSX and Darwin.

I too thought about OSX and Darwin when I saw this. Except that before, with Android, you had an open userland system on an open kernel. Now you have a huge binary blob that can do everything without control, on top of a open userland with an open kernel. It's a closed layer on top of two open layers. And the best of all, more and more things seem to depend on the closed layer instead of just on the other two. From what I see, as it "defrags" Google has been moving core functionality, previously open, into that closed-source Play Services thing. I think the plan is probably to take everything related to UX into the closed part, that Samsung, HTC and etc. won't then be able to change to create their own UX, and leave as open source the essentials needed for porting to new devices. I have mixed feelings about this... it's great if they manage to dismiss those who think there's a fragmentation problem in the platform. But they are doing it at the cost of decreased openness, and I don't like that.

Re: Google is defragging Android

#15

Notably, Play services is totally closed. So Google has abandoned the open source part of Android and is now developing the operating system as a completely closed product. Edit: downvotes don't change the truth of the observation. Android is no longer meaningfully open, other than a years old core of basic functions. Just like OSX and Darwin.

I remember when Android was starting to gain popularity (around 1.6 I suppose), one of the key decisions that I really liked was that Google apps would have no more access to the OS than any other apps. There was no preference to Google. This has now all changed.

Further, what's to stop other vendors doing this, possibly without users knowledge? How many users will click "allow" on a permissions box that gives the vendor a huge amount of permissions like this just so that they can use the latest MyTwitFace?

Re: Google is defragging Android

#16

Notably, Play services is totally closed. So Google has abandoned the open source part of Android and is now developing the operating system as a completely closed product. Edit: downvotes don't change the truth of the observation. Android is no longer meaningfully open, other than a years old core of basic functions. Just like OSX and Darwin.

I don't see the problem here. Play is part of Google's ecosystem, not the Android OS platform. I can download Android's source code, compile it and put it in any device I want (provided I have the technical capability to do so of course). In fact, this is what Android distributions like Cyanogenmod do, and they also provide a binary blob with Google's stuff as an option, if you want to install it. I don't see the reason to demand the Play store app to be open source nor what could be gained from it.

Re: Google is defragging Android

#17

It's worth noting how closely Android's apparent path going forward mirror's Apple's strategy with both OS X and iOS: closed end-user components built on top of an open source core. I guess Google's realized that "openness" isn't a meaningful market differentiator for the average consumer.

Google didn't choose the open-source route because it figured consumers would find that enticing. They did that to encourage development on a low marketshare platform. Android exploded in popularity in exchange for fragmentation.

Re: Google is defragging Android

#18

Notably, Play services is totally closed. So Google has abandoned the open source part of Android and is now developing the operating system as a completely closed product. Edit: downvotes don't change the truth of the observation. Android is no longer meaningfully open, other than a years old core of basic functions. Just like OSX and Darwin.

On the other hand, Google Play Services largely encompasses those features that were /always/ closed source in Android: maps, google+ and GCM. The Google applications that are core to the "standard" Android experience for most users have also always been closed source: Maps, Gmail, Google Calendar.

There are still a lot of new features being introduced to the core Android APIs, with fragmentation issues being mitigated by a provided support library [0] which essentially backports the newer APIs to older versions of Android (some new features are only in the support library).

Android as it's sold in most consumer devices obviously isn't entirely open, but Google still seem to be attempting to strike a balance between supporting the open-source platform on the other, and building up a suite of closed userland features on the other. You might disagree with their judgement on where the balance is, but I think it's unfair to say it's being developed as a completely closed product.

[0] http://developer.android.com/tools/support-library/index.htm...

Re: Google is defragging Android

#19

Notably, Play services is totally closed. So Google has abandoned the open source part of Android and is now developing the operating system as a completely closed product. Edit: downvotes don't change the truth of the observation. Android is no longer meaningfully open, other than a years old core of basic functions. Just like OSX and Darwin.

I remember when Android was starting to gain popularity (around 1.6 I suppose), one of the key decisions that I really liked was that Google apps would have no more access to the OS than any other apps. There was no preference to Google. This has now all changed. Further, what's to stop other vendors doing this, possibly without users knowledge? How many users will click "allow" on a permissions box that gives the ve…

Where has this changed? Google's apps are still built on top of the SDK. The only real change was the centralization of Google Play Services, but that doesn't change the level of OS access at all and 3rd-party developers can still tap in to these services.

Re: Google is defragging Android

#20
So, the ultimate nail in the coffin for open, fragmented services. If you want to build a good OS, you ultimately have to take almost complete control. (Google is basically following Apple's route.)

The reason I think the Google system is worse is that theoretically any application can achieve this level of control. So while I might trust Google, it seems all too easy to trick users into installing a different process which can take complete control of their phone. With iOS, only Apple is capable of this level of control, thus decreasing the attack vectors.

EDIT: Admittedly it's highly unlikely that Google would ever let such an application into the Play Store, thus limiting its distribution potential.

Post reply on HN