concept Google in category android

This is an excerpt from Manning's book Android in Practice.
A consortium of companies known as the Open Handset Alliance, led by Google, looked at the landscape several years ago and asked the question “What would it take to build a better mobile phone?” By better they meant a phone that could overcome the hurdles holding back widespread collaboration, innovation, and adoption on other platforms. The answer they came up with was Android. Android is a powerful and open platform that anyone can use and extend. Figure 1.1 shows a montage of screen shots that demonstrate a few of the platform’s capabilities.
Second, the Android framework classes package other open source libraries as part of android.jar, such as Apache Commons HttpClient and the JSON reference implementation from json.org (see chapter 9). Because those libraries are themselves artifacts on Maven Central, it’d be wasteful to package them within another artifact (Android, in this case). Hence, the Maven community stripped out those third-party libraries from the standard android.jar and instead declared dependencies to them. This can be seen in the Maven dependency browser in Eclipse (see figure 14.8). So why is this a problem? It’s a problem because sometimes, the versions of those libraries bundled with Android aren’t exactly the same as those available on Maven Central. Google is free to make modifications to them before bundling them with Android or to package a version that’s not available on Central. This has happened with the JSON library: the one on Maven Central ships with a different implementation of JsonStringer than the one in android.jar, which means that you may run into compilation errors when using that class while building against the android.jar from Central. Clearly, we must find a way to resolve these issues.