IoT Summit 2017 - Leverage W10 IoT Core on a Raspberry Pi to connect your sensors to the Cloud

Editor's Notes

• #4: Key messages: We believe our research in service of these three ambitions will lead to what we think of as an “invisible revolution”. Where increases in our capabilities are powered by technology that moves further out of sight. The innovation will come from the shift to the cloud…move from having device power right in front of you magnified and moved to the cloud. Invisible processing power, storage, intelligence, etc. The innovation will come from what’s happening inside and around the device versus the object you can see. Capabilities that come from machine learning, powerful algorithms, cloud, intelligence, and so on. The innovation will come from an ecosystem of computing that surrounds you. Pervasive computing which will become so natural, it disappears into the background. When technology becomes more powerful, but less intrusive, it can fit into more parts of our world and solve an even wider range of problems.
• #12: Windows 10 runs on a wide variety of devices, from phones with a 4.5” screen, through phablets, tablets, PCs, laptops, convertibles such as the Surface, on desktops and All-in-ones, to the Xbox in your living room and right up to giant 84” screens such as our team collaboration device, the Surface Hub. And it also takes in very tiny cheap computers such as the Raspberry Pi 2, and innovative hardware such as the Hololens.
• #13: We’ve divided this broad range of hardware into different device families – as developers you will likely build apps that target one or more device families. <click> We have small devices and IoT, phones and small tablets are in the Mobile device family, large tablets and PCs in the PC (or as we more usually call it, Desktop) family, the Xbox, Surface Hub (or ‘Team’) and finally the Hololens <click> And all of these device families run the same developer platform – the Universal Windows Platform. You can build a single app that can run across all these device families using a single SDK and distribute apps through a single store. Of course, with this diversity of devices, what we are *not* saying is that you should create one app that kind of works adequately across all these devices. No, we want you to create apps that shine on each device family, so we’ve added APIs, controls and tools to help you build an adaptive UI.
• #16: Key points To simplify looking at the 1000’s of IoT devices we can segment them many different ways. One way is by a class of device to look at them in terms of resource requirements and capabilities. Windows 10 IoT addresses key device categories for these purpose built devices.
• #17: Windows 10 IoT Enterprise. This edition is for industry devices like ATMs, thin clients, point of sale devices, medical devices, and industrial devices, providing the full capabilities of Windows 10 Enterprise – including the ability to lock down the device for line-of-business use and to support Classic Windows applications as well as Universal Windows apps. We recommend LTSB to support mission critical systems Windows 10 IoT Mobile Enterprise. This edition is for mobile industry devices like handheld terminals and mobile point of sale devices, providing the full capabilities of Windows 10 Mobile Enterprise – including the ability to lock down the device for line-of-business use and to support Universal Windows apps and additional integrated peripherals and sensors. We recommend Current Branch to keep these devices on the latest security and latest feature innovations Windows 10 IoT Core. This edition is for small footprint, low cost devices like gateways supporting Universal Windows apps. Windows 10 IoT Core is intended for single purpose devices and will not include the Windows desktop shell or apps like mail, photos, people, etc.. Servicing will not be available for these devices in the initial release. All shipped devices will be updated via wipe and reload method, if shipped. Optionally, manufacturers can continue testing these devices and postpone their release when servicing becomes available, if the customer deems it critical to utilize the servicing functionality.