1. Device Apps
Joseph Ngari| Program Manager

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

3. 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

4. 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

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

6. Big Picture

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

8. Big Picture
App Store
app
Metadata
meta

9. Big Picture
App Store
app
Metadata
&
Drivers
meta

10. Next Level of Detail

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

12. 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

13. 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

14. 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

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

16. 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.

17. 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

18. 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.

19. Submitting & Updating

20. Sequence for submitting
Driver
App
Meta-data

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

22. 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.

23. Platform Considerations

24. 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.

25. Recap

26. 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

27. 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.

28. Thank You!
Joseph Ngari| Program Manager