Hacker News new | ask | show | jobs
by jgs1 4651 days ago
As a satisfied user of the latest CyanogenMod nightlies on a 2 year old Galaxy S2, this is great news! CM has breathed new life into my outdated hardware.

However, I have to echo the concerns in the post's comments about Gapps[1] (Gmail, Maps, Play Store). I wouldn't say the dependency is as strong as something like Zynga/Facebook, but if Google ever chose to lock Gapps down, I don't know that I'd stick with CM.

[1] http://wiki.cyanogenmod.org/w/Gapps

2 comments

You can roll your own Gapps quite easy (before flashing a custom ROM) if at some point Google starts going after anyone and everyone distributing it (which is what they would potentially target if they did). I've done it before when compiling the AOSP source and there's nothing out yet because it's a new AOSP version.
Google currently has no incentive to lock down those apps. The one place that they have the least incentive to lock down is the Play Store, as CM users will still be sending money their way.
right but they do lock them down. As it says on the parent url, "Due to licensing restrictions, these [GApps] apps cannot come pre-installed with CyanogenMod and must be installed separately." Google heavily licenses GApps.

The incentive for them is to stop folks like Amazon installing Google Apps on their Android fork, and to encourage Chinese/3rd party/etc indie OEMs (the kind no-name tablets you see on eBay for $100) to establish a relationship with Google in return for then being able to supply GApps on their devices.

Holding the keys to GApps is what allows Google to give away the rest of the castle (Android) and still maintain control.

Except, much like Apple's walled garden approach, they want to ensure that what is in their app store works. Because if I pay for a product at your store, and it doesn't work, I complain loudly, demand things, etc. That's a headache to deal with, for Google, for the app developer and for someone using a stock phone looking at an app with terrible reviews.

So in a way, they do have an incentive to make sure that unknown builds can't access their app store.

It is a pretty easy distinction for users to make. Google can easily add a disclaimer that Google won't support or guarantee performance on non-Android devices. If they want to keep CM users happy about that they can offer trial versions so that users can test, or maybe even offer a money-back guarantee for an app.
Google does lock down the Google Play services, and their incentive for doing is the license fee$$$ they can charge to the compliant device manufacturers.