Windows Enterprise Desktop

Jul 29 2013   12:13PM GMT

Compelling Win8.1 Feature: Device-Friendly App Development

Ed Tittel Ed Tittel Profile: Ed Tittel

Though Windows 8.1 offers some very nice features and functions — and in some cases, ones that are absolutely vital (as with a reworked Start menu, and improved desktop access) to any hopes the OS might have for success and commercial uptake — so far, it’s been hard to find any truly compelling reasons to make the move to the latest and presumptively greatest entry in the ongoing series of Microsoft desktop operating systems. But here’s something to ponder along those lines, as discussion in the July 26, 2013 posting to the Windows App Builder Blog. Entitled “Building apps that connect with devices,” this post lays out the mechanics of bringing apps and devices together in very interesting ways to take advantage of touch on the PC side and all kinds of focused capability on the device said. Here’s a block diagram of what this new approach looks like:

win81-devapis

As it turns out, it’s the layers in the middle that make this incredibly interesting — and potentially quite valuable, for device makers and vendors — because they depend on what MS calls either device scenario or device protocol APIs. Here’s how the blog post explains these things: they “…allow a Windows Store app to talk to a device over industry standard protocols like USB, HID, Bluetooth (and Bluetooth Smart), as well as Wi-Fi Direct As a developer, all you need to do is simply identify the device (leveraging metadata) and then open a communication channel to the device. Opening a channel prompts for user consent.” And if such consent is granted (it’s required to prevent apps from accidentally or maliciously communicating with devices behind the scenes, without users being informed or aware of such activity), apps can communicate with devices — even those involving large data transfers, which can proceed even after a user changes focus to another app — as and when they need to.

This finally explains what MS was getting at when they disclosed that Windows 8.1 includes built-in facilities for driving 3-D printers (which have previously required dedicated device drivers for earlier versions of Windows). It also explains how MS can claim that “home developers can create their own apps to communicate with non-standard devices. The post concludes with pointers to a series of videos that dig into these subjects in more detail:

Interested readers will want to check out one or more of these items, depending on where their hardware and interface interests lie. Great stuff though, all around!

 Comment on this Post

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: