Building an app that connects to devices

2. Building an app that connects to devices • George RoussosSenior Program Manager • DeenKing-SmithProgram Manager • 2-023

3. Meet the Ramirez family • Will buys a smart toy for Toby online using a fingerprint instead of a password • He prints a home design on a 3D printer for a customer visit tomorrow Will—Architect Sarah—Real estate agent Toby—Teenage son June 26th 2014

4. A day in the life of a modern connected family • Will’s tablet shows his agenda upon arrival at the customer location. • Sarah tracks and uploads her steps to keep her new year’s resolution. • Toby unboxes the smart toy, connects it and controls it.

5. Windows 8.1 provides new opportunity to build compelling apps that connect to devices across desktops, laptops and tablets.

6. Agenda • Windows 8.1 enhancements. • Expands access to devices. • Adds user experiences. • Simplifies the developer experience.

7. Windows 8.1 expands access to devices

8. Remember Will? • New APIs in Windows 8.1 simplify app development for specific scenarios.

9. Device scenario APIs New device scenario APIs in Windows 8.1 • Any app can access devices with scenario specific APIs for devices Windows knows about.

10. What about Toby and Sarah? • New Windows runtime APIs for familiar industry standards like Bluetooth and USB enable low cost app development for custom devices on all Windows 8.1 desktops, laptops and tablets.

11. Introducing device protocol APIs App • Windows Runtime APIs: • Bluetooth (RFCOMM). • Bluetooth Smart. • HID. • USB. • Wi-Fi Direct. Protocol: left, right, fire HID API Class Drivers Device

12. Device protocol APIs for hardware developers • Expose unique hardware functionality as a protocol over these APIs leveraging Microsoft drivers. • Publish that protocol to software developers to enable an ecosystem of apps for external devices. • Create and publish a Windows Runtime Component to simplify app development for complex devices.

13. Device protocol APIs New device protocol APIs in Windows 8.1 • New Windows Runtime APIs: • Bluetooth (RFCOMM). • Bluetooth Smart. • HID. • USB. • Wi-Fi Direct. Innovative Devices Ecosystem of Apps Independent Developers

14. Windows 8.1 adds new user experiences

15. New user experiences for custom devices • Launch on Connect. • Syncing data with a device in the background. • Users in control of devices and personal info.

16. Launch on Connect • Autoplay launches a recommended app when a USB peripheral is connected. • Hardware developers must opt-in to Autoplay for their device. • Any software developer can then enable Autoplay.

17. Syncing data with a device in the background • Device Background Tasks lets an app complete a user initiated sync operation for up to 10 minutes in the background. • Any app can include a background task to enable this scenario.

18. Users in control of devices and personal info • User consent puts the user in control before using apps that can access privacy sensitive data. • Any app using Bluetooth, HID, or USB APIs must declare new device capabilities in app manifest.

19. Windows 8.1 simplifies the developer experience • Deen King-Smith • Program Manager

20. Developing in Windows 8.1 Visual Studio Express 2013 SW dev Windows Store app Windows runtime component Device scenario APIs Device protocol APIs HW dev Hardware

21. Device scenario APIs Windows Store app • Same as in Windows 8. • Just use the Namespace and the API, Windows does the rest. • Scenarios. • Fingerprint, scanner, geo-location, and more. • Need to know. • App development. • APIs. Device scenario APIs //Create the scanner object ImageScannermyScanner // Scan API call to start scanning myScanner.ScanFilesToFolderAsync(ImageScannerScanSource.Default… Hardware

22. Device protocol APIs Windows Store app • APIs simplify custom device access via industry standard protocols. • Scenarios. • Sports Watch, Missile Launcher, or any Custom Device. • Need to know. • Specific protocol details for the device. • Industry standard protocol. Device protocol APIs Hardware

23. Toby’s missile launcher

24. Ecosystem of apps via protocol APIs Windows Store app • Hardware developers can provide a Windows runtime component to enable an ecosystem of apps. • Scenarios. • Sarah’s fitness device, and more. • Need to know. • Hardware developers—Specific protocol to create the runtime component. • App developer—API from the hardware developer to use the runtime component. Windows runtime component Device protocol APIs Hardware

25. Differentiating your User Experience Windows Store app • Hardware developers can enable additional device specific scenarios with device metadata. • Scenarios. • Autoplay and more. • Need to Know. • Hardware ID. • Submission to Windows Hardware DevPortal. • App information. • Device metadata. Device metadata HW dev Hardware

26. Device metadata & app development 2nd 3rd App development 1st Submit app Reserve your app name Experience ID Add Experience ID to app Add app info to metadata 2nd Device metadata development 1st 4th App info Experience ID Submit to HW dev portal Submit metadata

27. Windows 8.1 Enhancements The Ramirez Family • Expands access to devices. • Adds user experiences. • Simplifies the developer experience.

28. Resources: device scenario APIsAny app can access devices with scenario specific APIs for devices Windows knows about

29. Resources: device protocol APIsDevice protocol APIs enable apps for custom peripherals that Windows does not know about. Anybody can develop apps for a custom peripheral if they know the device protocol to do so.

30. Required Slide *delete this box when your slide is finalized Your MS Tag will be inserted here during the final scrub. Evaluate this session • Scan this QR codeto evaluate this session and be automatically entered in a drawing to win a prize!