Microsoft is making more IoT plays than its Insteon compatibility projects and Cortana voice control for the home. It has now joined the likes of IBM, Intel, AT&T, Cisco and GE in the Industrial Internet Consortium; a group focused on ‘transforming industry through intelligent, interconnected objects.’ It’s also released its SDK for Windows IoT.
We’ll tackle the former first, which preceded Microsoft joining the AllSeen Alliance last week. Both industry bodies aim to encourage IoT progress by developing interoperable standards and common architectures, but neither has announced compatibility with the other. This looks more like Microsoft hedging its bets on rival bodies, staying in the loop rather than choosing a side and sticking with it exclusively. Cisco is a member of both bodies too, and Samsung can’t seem to say no to joining a new club.
But Microsoft does have significant bets to hedge, namely its Azure cloud platform, which combines machine learning with the more typical device and system management tools you expect in a cloud service. Microsoft’s GM for IoT, Kevin Dallas, said that Azure ‘represents our most recent example of investments we’re making in a comprehensive and robust M2M/SCADA (supervisory control and data acquisition) platform to power the internet of things.’
Dallas went on to add ‘these are industry challenges. No single company will solve these problems, and the need to make sure we are on the right path together is stronger than ever as new devices and services are launched almost every day. In many ways, our opportunity is similar to the early days of the web. Imagine if the http protocol was not a standard adopted by everyone.’
Given that Microsoft is laying off 18,000 staff as it tries to concentrate on its software businesses and cloud services. Given that 12,500 of the cuts will come from the Nokia division that new CEO Satya Nadella inherited from the infamous Ballmer, the move shows Nadella’s drive to focus the company not on mobile devices but on mobility and connectivity from anywhere with an internet connection. This is the foundation on which Microsoft will be building out its IoT divisions.
And when Dallas says ‘we believe the promise of IoT lies in making new and existing devices smarter by connecting them to services in the cloud,’ we can see the plans that Microsoft has for the future; becoming a cloud giant and the link between as many devices as possible ‘ a ubiquitous service. Well what better way to get that ball rolling than by launching an SDK for the as-yet-unnamed-but-almost-certainly-going-to-be-called Windows IoT.
The SDK represents another attempt by Microsoft to get Windows on embedded devices, after the slightly botched Windows Embedded x86. At the Build keynote back in April, Terry Myerson, Microsoft’s EVP of Operating Systems, showed off an Intel Galileo developer board while singing Intel’s praises. The 32-bit x86 Quark SoC found in the Galileo prompted Myerson to ask ‘what kinds of devices are possible when a PC runs on something the size of an eraser?’
Well the developers are about to find out, so long as they’ve followed the advice given at the Build conference and bought a Galileo board. But the new SDK has been confusing some early adopters as Microsoft appears to have taken a few steps backwards.
Paul Thurrott of WinSuperSite has pulled apart the SDK and found that ‘instead of being based on some modern .NET or Windows Runtime-type framework, this first version only supports C++ and, amazingly, the once-deprecated Win32 API. This is basically how Windows apps were developed in the 1990s folks. The .NET framework first appeared in 2002.’
While this seems a little mad in terms of using decades old programming interfaces for the bleeding edge of connected devices, Thurrott notes that Microsoft is planning on actually implementing the Universal app model it unveiled at Build. The earlier languages may also prove a boon for the lightweight device specifications that IoT apps will require, but C++ is a very popular programming language among software engineers regardless.
Thurrott also pointed out that although you can make W-IoT apps in Visual Studio, the apps can only be run on the Galileo, instead of the usual virtual machine emulators that are available for Windows Phone and Windows 8. While the SDK is free for developers to use, after sitting on a waiting list, developers will no doubt be waiting for a UI to be introduced, instead of the current command line interface, as well as expanding the supported languages beyond the Win32 and Arduino Wiring subset currently available.