Microsoft Windows Mobile vs Google’s Android for Ruggedized Handhelds

With Microsoft having announced that Windows Mobile is going to be supported by Microsoft through to 2019. building on existing investments in this cost climate has major benefits to many local government users. It is also probably fair to suggest that most customers are more familiar and comfortable with Windows Mobile than any other mobile operating system.

This leaves many wondering which should be the right choice for Ruggedized Handhelds?

The following report by Gartner covers some interesting points to consider.

‘Choose Windows Mobile over Android for Ruggedized Handhelds’ - Ken Dulaney, Tim Zimmerman, William Clark

The uncertainty regarding the future existence of Windows Mobile and CE, after recent Microsoft announcements, has introduced confusion, and is affecting device requirements for enterprises looking to "derisk" their ruggedized device decisions by also looking at Android. This research looks at why organizations that depend on ruggedized handhelds should not consider an OS change.

Key Findings

• During the past year, Microsoft moved Windows Mobile and CE mobile OSs and tools from the group focusing on mobility to the embedded group and, most recently, to the server group. These moves have confused handheld OEMs and customers.
• OEM vendors are considering the Android smartphone OS to supplement their Windows offerings. The uncertainty about Windows OS offerings, the rise in popularity of Android and the need for vendor differentiation are motivating factors for the change.
• The development of new processor technology and increased memory will give vendors the option to use other variants of the Windows product family for the next-generation handhelds, if there are issues with Windows Mobile or CE.

Recommendations

• Remain with Windows Mobile for ruggedized handheld-computer solutions, and to prepare for a transition to full Windows in subsequent implementations.
• Choose application development tools and architectures to maximize future application flexibility and minimize porting costs to Android or future versions of Windows.
• Review the Microsoft embedded systems road map annually. Enterprises need to track the capabilities and maturity of OS options, and re-evaluate opportunities and risks if Microsoft fails to deliver or competitive solutions provide better differentiation.
• Limit the scope of Android-based ruggedized application development through 2013. Ensure that applications clearly separate standard Android from OEM Android extensions.

Strategic Planning Assumption(s)

• By YE11, native development will be extended (primarily through the Android NDK, with some layers abstracted through Java), which will entail building APIs from the ground up alongside either third-party or custom-made management and security software.
• By 3Q12, native support will be provided by mobile enterprise application platforms, such as SAP-Sybase, Antenna Software, Syclo and Spring Wireless.
• By 1Q14, native support for Android devices will only come from a small niche of packaged mobile application platform vendors. This is because, on average, the R&D resources available to these vendors will be fewer.
• By 2Q13, HTML5-based rich client applications from enterprise software vendors will add a layer of abstraction that will make applications suitable for ruggedized devices that don't push the envelope for peripheral support. We also expect some spillover from the mainstream smartphone market, in terms of peripheral support and openness.

Prev - Next >>