Device Apps Joseph Ngari| Program Manager

Windows 8 makes it easy to bring your device and your software together

Value of a Device App Your code gets into your customers’ hands… automatically You own all the pixels You can naturally integrate with built-in Windows experiences You can use custom functionality from your device & driver You have the power of easy & comprehensive tools

How device software was acquired in the past Package comes with instructions that point to CD or Internet User installs CD or navigates to web to download software. Setup wizard starts and user accepts Eula and clicks “Next” button as quickly as they can. Software is installed in start menu and you place an icon on the desktop

How Device Apps are Acquired in Windows 8 Plug in device App is automatically downloaded Driver is automatically downloaded (if you have one)

Big Picture

+ + + meta app meta Components Device Device driver Device metadata Software components meta app + + + meta Device Device driver Device metadata Device App

Big Picture App Store app Metadata meta

Big Picture App Store app Metadata & Drivers meta

Next Level of Detail

Identifying the device Developer specifies a Plug and Play ID… …and adds it to the device to report to Windows

Identifying the app and the device metadata Exp ID Developer generates a GUID as the device experience ID Developer adds device experience ID to app Developer adds device experience ID to device metadata app meta

Binding the driver, metadata and app + Sysdev verifies certification of device & device driver Sysdev verifies device ID meta Microsoft signs the device metadata package Sysdev verifies device experience ID in app app Store validates app

A device experience coming together Windows reads device ID Windows matches the device ID to the device metadata & installs it Windows matches the device ID to the device driver & installs it meta Windows reads the app info from device metadata & installs the app app

Big Picture Revisited app meta App Store Metadata App ID Info Device ID

Binding the Device and the Meta-data The device has a Plug and Play ID Add the Plug and Play ID to the meta-data When the device is plugged in the meta-data is automatically downloaded.

Binding the App and the Meta-data App provides App Information (Package Name, Publisher ID, App ID) Meta-data wizard creates Experience ID Cross link app information and experience IDs. You add App ID to the meta-data You add Experience ID to the app

Driver and Restricted APIs Restricted Interfaces and Privileged Apps A custom driver interface is a restricted interface. Only one application gets to access this this interface. It is called privileged App. Accessing Restricted API App declares custom interface ID in appmanifest Meta-data marks the app as privileged. When app tries to create device broker ensures that the app is privileged and that the custom interface being accessed is the custom interface that was declared in the appmanifest.

Submitting & Updating

Sequence for submitting Driver App Meta-data

Where to Submit App App Store Meta-data and Driver Sysdev

Updating App: Meta-data is automatic Driver update is manual Updates are handled through the built in Store app. Meta-data is automatic Every 5 or 8 days. Driver update is manual Must ensure that the driver and app can function independently and also handle version differences. Use your application to notify user when a new driver is needed.

Platform Considerations

x86/x64 and ARM IHVs can submit drivers for x86 and x64 IHVs cannot submit drivers for ARM Must partner with OEMs to do this.

Recap

Recap Windows 8 makes it easy to bring your device and application together Meta-data binds the hardware and the app together 1:1 mapping of app and driver

FAQ Is the app discoverable in the store without the device? Yes. It is an opportunity to invite to learn about and buy your device. If they do have the hardware they can plug it in and it will work. Can you support different devices with the same app Yes. Different meta-data packages can point to the same application. Can a device auto acquire more than one app? A device can have only one auto acquired app Does the device need to be certified? Yes. Validation of the meta-data involves checking that the referenced device is certified. Can an IHV require that the user pay for the automatically acquired app? The automatically acquired app must be free. They app can have in-app purchases.

Thank You! Joseph Ngari| Program Manager