them. Additionally the different components are distributed through different services, with different policies and latencies: App updates are available sometime after being accepted. Users are notified when app updates are available and can download them through the Windows Store app. Device metadata updates are available 48 hours after being accepted and are downloaded automatically for new devices connected to the PC. Device metadata for the PC is automatically updated by a Windows maintenance task every 14 days. Driver updates are available sometime after being accepted, depending upon Windows Update client settings. Users are notified of these optional updates if they check Windows Update, where they can download and apply the driver. The driver can be available as soon as 24 hours, depending upon those settings. Because of the availability time differences, it's likely that the app, device metadata, and custom driver may be of different versions. Components need to cope gracefully if any companion components are unavailable. Only the OEM can deploy device metadata updates to the PC device container. All parties need to be in close communication about the contents of the privileged app fields and driver functional contracts. The component supplier can submit updates to the app and driver to Microsoft portals, but the OEM governs metadata. It's important to understand that Windows 8.1 doesn't automatically install a new driver over an old driver. Aside from that, the sequence for updating your Windows Store device app is the same as the sequence you used to submit it. Design Patterns for Specialized Devices This table summarizes design patterns for different types of devices. You can choose a design pattern based on the protocol used to communicate with the device and the type of device driver. The table also identifies which design patterns have restricted interfaces. The main steps in the planning and implementation of each design pattern and which Windows Runtime APIs to use are outlined after the table. Summary of PC Internal Specialized Device Design Patterns Design Patterns Pattern: WPD with Custom Driver Summary: Intelligent device with functionality that fits into a well-defined object model with properties.
them. Additionally the different components are distributed through different services, with different policies and latencies: App updates are available sometime after being accepted. Users are notified when app updates are available and can download them through the Windows Store app. Device metadata updates are available 48 hours after being accepted and are downloaded automatically for new devices connected to the PC. Device metadata for the PC is automatically updated by a Windows maintenance task every 14 days. Driver updates are available sometime after being accepted, depending upon Windows Update client settings. Users are notified of these optional updates if they check Windows Update, where they can download and apply the driver. The driver can be available as soon as 24 hours, depending upon those settings. Because of the availability time differences, it's likely that the app, device metadata, and custom driver may be of different versions. Components need to cope gracefully if any companion components are unavailable. Only the OEM can deploy device metadata updates to the PC device container. All parties need to be in close communication about the contents of the privileged app fields and driver functional contracts. The component supplier can submit updates to the app and driver to Microsoft portals, but the OEM governs metadata. It's important to understand that Windows 8.1 doesn't automatically install a new driver over an old driver. Aside from that, the sequence for updating your Windows Store device app is the same as the sequence you used to submit it. Design Patterns for Specialized Devices This table summarizes design patterns for different types of devices. You can choose a design pattern based on the protocol used to communicate with the device and the type of device driver. The table also identifies which design patterns have restricted interfaces. The main steps in the planning and implementation of each design pattern and which Windows Runtime APIs to use are outlined after the table. Summary of PC Internal Specialized Device Design Patterns Design Patterns Pattern: WPD with Custom Driver Summary: Intelligent device with functionality that fits into a well-defined object model with properties.
Windows%20Store%20Device%20App%20Design%20Guide%20for%20Specialized%20Devices%20Internal%20to%20the%20PC.docx