Here’s how Google plans to reduce update cycles and fragmentation in Android

The Android Compatibility Definition Document (CDD) is a list of rules by Google, which Android OEMs need to follow in order to get their devices approved for Google services, which includes the Google Play. The document is released each time a new version of Android is announced, and the one for Nougat is finally here. Interestingly, Google seems to be using this to reduce the fragmentation between hardware and software, which has always been the secret sauce to the iPhone’s performance.

Firstly, the CDD mentions something called Android Extensions, which is mandatory for all OEMs. Google may use these to bypass OEMs and carriers when pushing updates to its AOSP APIs. Currently, such updates need an update to the entire Android ecosystem. However, the Android Extension APIs on the LG V20 and Google Pixel don’t reveal much at the moment.

To make it simpler, one must understand the two sets of APIs on Android right now. There’s the AOSP APIs and Google Play Services APIs. While Google can update the Play Services APIs any time, updating AOSP APIs on a third party device takes time. This is because of the modifications etc. that are done by OEMs. By using Android Extensions, Google is trying to nullify this issue.

Further, Google has also issued a “strong recommendation” to use USB Power Delivery standards, instead of the myriad proprietary charging standards in the market. Some examples of proprietary standards in this area are OnePlus Dash Charge, OPPO VOOC charging and Qualcomm’s Quick Charge standards. Google uses USB Power Delivery in its Pixel devices, and that is what it is recommending for all Android phones. While it is only a recommendation right now, speculations are that later versions of Android may make it mandatory, thereby allowing users to charge any phone with any charger.

The CDD also has rules for standard functions from inline buttons on earphones that attach to the 3.5mm jack on Android phones. This would be useful, since it would allow all headphones to function similarly with each Android phone, however, one cannot overlook Apple’s recent push at obliterating the jack altogether.

There’s also a provision for the multi-window facility introduced in Android Nougat. While this feature has been implemented by other OEMs much before Google, the Search giant is now preventing them from using any other method but its own. OEMs can still choose to not use the feature, but they can’t use their own versions.

With all the changes mentioned above, Google’s goal seems simple — to gain more control over Android. The open source nature of Google’s operating system has allowed OEMs to build phones using Android very easily, but it also takes away the control from Google. Currently, problems with OEMs not issuing updates, or hardware compatibility are issues that put Android behind iOS. Google seems to be slowly implementing this. However, it is still far from the vertical integration that an iOS-powered device enjoys.

Note: The CDD also reveals that Vulkan APIs aren't necessary for Android Nougat implementations. This again raises questions on why devices like the Nexus 5 etc. will not be getting the update. Vulkan compatibility was earlier thought to be the reason for Nougat being pulled from such smartphones. While Android Nougat does support Vulkan APIs, it doesn't make the same mandatory.

Follow Us

Prasid Banerjee

Trying to explain technology to my parents. Failing miserably. View Full Profile