So, the Technical Account Manager for Android at Google came for the department’s seminar session. She’s basically in charge of Google’s relationship with manufacturers that use the Android OS. First off, Google is not the soul creator of Android. It’s actually a creation of the Open Handset Alliance, a group of handset manufacturers, software developers, cell phone service companies, etc.
The Android OS, despite being less than a year and a half old, has fragmented to an appalling degree. Different manufacturers include varied screen sizes, sensors and actuators. So, application developers cannot predict what hardware is available. And consumers cannot easily predict if an application they download will function correctly.
The operating system itself has even become fragmented. There are five different versions of Android available across different hardware. Developers now have to consider these different versions, not unlike working with different browsers. Developing for the latest version (as Google does), effectively tells anyone with an older version (79.6% of the Android market at the moment) that they’re out of luck.
I will note that the speaker suggested using version 1.5 or 1.6 rather than 2.1 in developing. On the one hand, that does solve a short term problem of diverse systems. On the other, it makes an unsafe assumption of developers: that we’d want to use an older specification. For most programming languages, it is better practice and makes a person more employable to use the latest standard whenever possible.
And, there are some genuine reasons for this fragmentation. With more varied hardware, it becomes increasingly difficult to include the appropriate drivers (needing to write one for every new feature for every individual piece of hardware). Some devices do not contain the memory or processing to be upgraded, which effectively keeps them trapped with their original version.
It’s this fragmentation that will eventually lead to different flavors of the Android OS, more or less defeating the purpose of a unified operating system. Manufacturers may want to consider having an easy Lego-like means of upgrading hardware, but that still does not account for building the drivers (and assumes that manufacturers would even want open hardware).
Ah well. It was a nice idea.
Tags: develop, engineering, Industry, mobile, testing
