Together with Apple’s iOS, Android has helped to redefine expectations with regard to user interaction and functionality in the smartphone space. The widespread success of Android and iOS are among the major factors contributing to changes in OS strategy on the part of traditional market leaders Nokia (a shift from Symbian to Windows Phone) and Research In Motion (acquisition of QNX Software Systems and shift to a QNX-based platform). Furthermore, the ubiquity of smartphones has begun to impact UI expectations in other devices classes, with interest in utilizing Android to serve these requirements continually mounting.
But while interest in Android beyond smartphones (and tablets) has been widespread, actual deployments of other types of Android-based devices have remained somewhat scarce.
So where exactly are we today with regard to Android’s penetration in other areas?
According to our recently published report Android in the Embedded Systems Market, less than 5% of all Android-based unit shipments in 2011 were products other than smartphones, tablets, and eReaders. Among those device classes included within these estimates are military communication devices, medical devices, and connected car systems.
Because of Android’s many pre-integrated components – GPS, wireless radio, camera – the platform is a logical solution for mobile communication devices used by the military. These types of communication devices – such as a wearable rugged computer made by GD Itronix – comprised slightly more than 1% of this market in 2011. Clearly, the use of Android within military communication devices is still in its infancy, with the potential security vulnerabilities associated with an open source platform having contributed to the relatively slow rate of adoption thus far.
When Android was first discussed as a potential fit within non-consumer devices, the medical device market was frequently cited as an area that would benefit from the user interface and graphics capabilities of the platform. Despite this interest, few OEMs have elected to include Android in their designs, and initial uptake has been slow. VDC believes that a reluctance to augment legacy designs to include Android and complications around deploying the platform in devices with real-time requirements have been the primary inhibitors to broader adoption of Android within this market. However, new use cases such as patient entertainment systems continue to emerge.
While the GENIVI Alliance has garnered much of the attention around Linux-based platforms for OEMs’ automotive in-vehicle infotainment (IVI) platforms, Android-based IVI systems have begun to appear in the form of aftermarket solutions such as the Clarion Mirage (which runs a version of Android 2.2 customized by Wind River.) VDC expects that ongoing investments and relationships between major automotive OEMs and leading IVI solutions providers such as Microsoft and QNX Software Systems is likely to limit the adoption of this platform directly by OEMs. However, low-cost, highly functional aftermarket solutions enabled by Android offer consumers the ability to upgrade from lower-end factory-installed systems that do not take advantage of the latest in IVI innovations.
The strengths of Android make the platform a strong fit in a wide range of product categories. To date, Android has been deployed in devices ranging from televisions and set-top boxes to HMI applications in the industrial space, digital signage solutions, watches, and even ski goggles. As the effectiveness of Android beyond smartphones and tablets becomes more readily accepted, we believe new use cases for Android will continue to emerge and fuel the platform’s growth path.
However, many challenges – such as security, fragmentation, and legal issues – still remain. VDC investigates these and other trends in our recently published report, Android in the Embedded Systems Market, from our research service Strategic Insights 2012: Embedded Software & Tools Market. Please contact us for more information.
Comments