Android A to Z: What is the AOSP?

AOSP is a term you will observe used a great deal -- here, in addition to at other Android-centric sites on-line. I'll admit I'm accountable for using it just expecting everyone to determine what I'm speaking about, yet i shouldn't. To rectify that, a minimum of a little bit, I'll attempt to explain what the AOSP has become so we're all on the same page.


For many of ourselves -- the nerdly types who build software -- the complete name tells us the issues we need to find out. AOSP signifies Android Open Source Project. The AOSP was designed and written by individuals that included a vision the world needed an open-source platform that exists for developers to easily build mobile applications. It wasn't created to beat any other platform in popularity and revenues, as well as to function for user freedom from tyrannical CEOs -- it exists being a delivery mechanism for mobile apps -- like Google's mobile apps, or another of your 400,000 inside the Google Play store. Luckily, Google realized that using open-source software would ensure until this operating system/mobile application content delivery system is available for all, at no cost. And by choosing the licensing they did, it will be attractive to device manufacturers who will apply it to be a base to develop their own personal mobile OS. 


The premise plays out rather nicely. Google writes and maintains a tree of every the Android source code -- the AOSP. It's made for all (you, me, manufacturers you've never heard of and not simply big players like Samsung or HTC) to download, modify, and bring ownership of. This means the parents at CyanogenMod will add cool stuff like audio profiles. Moreover it means folks like HTC can change multitasking this kind of a number of ourselves detest. You can't posses one without having the opposite. The massive players then use their modified element of this source to construct their own os. Some, like Amazon, radically changed everything without a care to use Google's official applications and continue their device which complied with Android guidelines. Some, like HTC radically changed everything yet followed the Android Compatibility Program (ACP) in order that they may include Google's core application suite -- such as the Google Play store. Some, like the folks at CyanogenMod, boost the pure AOSP code with additions but don't change the overall look and feel. Again -- that's how this open-source thing works. You can't have without allowing folks to change it as they see fit, whether good or bad.


Everybody can download and gain the AOSP. We can easily even stay compliant with all the ACP and contact Google about including their applications. Yes, any of us could build our own device by using the AOSP code in your garage or basement with Google's full blessing. That's the beauty of the AOSP, and then we wouldn't want it other way.

Writer : Chin Keat

Article Android A to Z: What is the AOSP? is published by Chin Keat on Tuesday, May 22, 2012. 0 comments: in post Android A to Z: What is the AOSP?
 

0 comments:

Post a Comment

ShareThis