The future of Android: New compatibility requirements push for a more unified Android experience
The company recently pushed out the latest version of the Android compatibility definition document, which outlines the rules Android manufacturers are supposed to play by. It reveals a lot about the many different ways Google is going to nudge everyone who makes hardware to play by the same set of rules.
Why this matters: This Android document gives a lot of clues to the future of Android. It reveals that Google is making a number of steps to try and rein in an ecosystem that can sometimes go rogue given how different manufacturers fiddle with Android.
Fast charging standards
USB-C was supposed to usher in an era of easy and compatible charging. Instead it’s been kind of a mess, particularly with fast charging. To fix this, it’s now “strongly recommended” that device makers don’t push proprietary standards, such as Qualcomm’s Quick Charge 3.0. Additionally, the document says that eventually Android may require interoperability with standard chargers. Notice served that Google wants to push a future of better charging compatibility.
Something called “Android Extensions” could be another shot against fragmentation. Ars Technica theorizes that Google could use this to push APIs from the Android Open Source Project directly. This would work much the way that Google Play Services can be updated without going through the lengthy Android update process. OEMs wouldn’t be allowed to tinker or customize this in any way. It’s a complex feature, and one we’ll have to learn more about over time as it’s implemented.
A proper multi-window mode finally arrived with Nougat, but now it looks like there’s more pressure to actually do it in a less proprietary way. The document includes the following:
A device implementation MAY choose not to implement any multi-window modes, but if it has the capability to display multiple activities at the same time it MUST implement such multi-window mode(s) in accordance with the application behaviors and APIs described in the Android SDK multi-window mode support documentation and meet the following requirements.
One place to watch this is for the Nougat beta, which Samsung is rolling out now to Galaxy S7 and S7 Edge devices.
This will be good for application developers, who don’t want to support several different multi-window APIs, modes, and features.
Additionally, all Android manufacturers must implement some type of call blocking. This includes a tool for you to manage which calls are blocked. Many phones do this already, but Google’s making sure all Android users will have this basic feature.