The newest buzz in the world of Android is the whole Google vs. Cyanogen business. What’s going on? Where do we go from here? In the next few paragraphs, I try to explain the situation and throw in my two cents on the matter.
What/Who is Cyanogen / Cyanogen Mod?
Cyanogen (Steve Klondike) is an independent developer who has been creating custom roms for the Google Android operating system. His roms bring all of the functionality and features of Android and add additional functionality, while providing a stable, production grade environment that runs smoother and faster than the default Android build.
Really? So what’s the problem?
Cyanogen’s rom (and most other mods for that matter) use proprietary Google Applications (Google Maps, GMail, Google Android Market). These proprietary bits are necessary for the Android experience (imagine using Android without syncing with your Google phonebook, or being able to browse the Android market apps, etc, etc). Because those proprietary bits are closed source, what Cyanogen is doing is technically illegal. Hence the Cease and Desist letter Google sent Steve last week.
Understandably there has been a large backlash in the Android Community. Android was created supposedly with the idea of being open source, open to the community to do with it what they see fit, open to experimentation, open to tweaking, open to progress. However, as a commercial product, it becomes more and more closed. (Some) Applications are closed source (hell I don’t disagree with this… developers have to get paid too), areas of the platform are difficult to modify, so on and so forth.
So what do we do?
First we have to get past the reactionary phase. Calm down a bit and look at things rationally. Give me a second to rant so that I may move on in the next paragraph…
Google: get your head together and provide better answers to the community, especially developers. You’re getting some damned bad press here guys. If you kill your own brainchild by being obstinate to a guy who is improving your platform, you’re no better than certain software fruitcakes from Cupertino and the software tyrants from Redmond. If this is not resolved it is time to go to go, do not collect $200 and rename thyself ‘Macrosoft’.
Ok… now that that is off of my chest, lets explore the paths that lead from here:
Abandon ROMS: Not going to happen. ROMs improve Android greatly, making it run faster than before, use less battery power than before in some instances, and improving the overall quality of the Android platform. We’ll get athletes to stop using steroids first. We’ll get politicians to stop cheating on their wives first. Shoot… we’ll get me to start my homework on time first before that happens.
Ditch Google Proprietary Bits: This is the route that’s being taken for the moment. Cyanogen is making a custom ROM without Google bits and is aiming to provide those bits from alternative applications. Hello alternative market. Hello alternative to Google Maps. But this will make people think thrice about rooting and moving to a Mod. The Google Android experience is built partially on these bits.
Work it out with Google: This requires some corporate cooperation from Big G. How about a deal that allows these bits to be used by Cyanogen or Android Rom Devs in general? No? Ok… how about hiring Cyanogen so that he can keep working, this time making ‘Tools’ that can optionally be downloaded by enthusiasts such as myself who would like to push the envelope of my Android’ phone’s operation?
A side note… if you liked Cyanogen’s work, check out the Save CyanogenMod application in the Android market:
Price: Free |
I’ll continue to monitor this situation with reserved displeasure and slight annoyance. As always… feel free to comment below to tell me how you disagree with me or include your POV.
