Ever since Androids release in 2007 it has suffered horribly from growing fragmentation – different versions on tens of thousands of different devices – and gained an unintended reputation as a security disaster. Android 7.x Nougat is where Google must draw a line in the sand if Android is to thrive.
Google declaring minimum specifications will not stop all the problems because Android has escaped into the wild and there are no licensing fees for earlier versions. But Google’s 85-page Android 7.X compatibility definition may at least bring the larger players into line.
The document states, “This document enumerates the requirements that MUST be met for devices to be compatible with Android 7.0.”
The standards include handheld (touch screen and battery powered), TVs, Watches, Automotive, and Other. What is missing from this “Carrot” approach is any mention of the “Stick.”
{loadposition ray}
Interestingly it may spell the end to a broad range of customisations and third party apps as Google asserts that its own apps including Clock, Browser, Calendar, Contacts, Gallery, Search, Launcher, Music, and Settings must be used as they are exposed to other applications, implicitly or explicitly, through the Android implementation.
It says that it will allow each app to be overridden by third-party applications – not sure how that works but those apps must have similar settings and be compatible with Googles.
All graphics must support Vulcan and OpenGL ES 2.0; their browser must provide a complete implementation of the android.webkit.Webview API which means using Googles’s Chromium as a base. All search must use Google’s search and Text to Speech APIs.
In a hardware sense, it specifies minimum 4GB RAM, screen resolutions, 64-bit processors, Wi-Fi and Bluetooth LE, NFC, should have a fingerprint sensor, at least a rear camera, and all devices should be called by APIs.
USB has received special attention including auto-detection of 5V 1.5A and 3A, and it strongly recommended that USB should be USB-C 3.1, must have OTG host mode, and USB digital audio (to eventually replace the 3.5mm audio which is still recommended).
It strongly discourages Quick Charging except for new Universal Power Delivery standard (not Qualcomm) as used on the Pixel/XL. This is good as it will reduce incompatibility of various fast charge technologies and chargers which at present is a real issue. Power saving and doze must be standard.
There is a whole new section on VR, and the device must support at least the low level of stereoscopic rendering. At the high-end, it specifies High-Performance VR.
Comment
The 85-pages also address security and privacy including information collection.
I don’t recommend you read it but know that Google needs to do this or Android faces extinction. But the document gives a lot of clues to the future of Android and some of the rationale as to why device manufacturers must toe the line.
I don’t think it will have a lot of impact in mid-to-high-range devices as these will typically use established chipsets (that cover much of the new standards), but I suspect it will reduce the propensity for manufacturers to do too much skinning/customisation to Android. Pure Android or a light touch over thereof with rapid updates will become the standard buyers expect.
And if you think fragmentation is not an issue read OpenSignals report (2015) – while out of date it is eye-opening. Or read Android Developers dashboard stats here.
Now that Microsoft and Apple have full control of their Oss its time for Google to do so too.
