The component supplier submits device driver to the Windows Dev Center hardware dashboard for certification and distribution via Windows Update. The OEM passes the (Windows App Certification Kit) (WACK) tests for their app that incorporates functionality from the component supplier. The OEM submits the app to Windows Store. The OEM submits the device metadata package to the Windows Dev Center hardware dashboard for distribution via Windows Metadata and Internet Services The OEM can now preload the certified and digitally signed device driver, device metadata, and app. When submitting a privileged app for a PC internal device for Windows Store download, follow the instructions in , but remember that the metadata in this case is the device metadata package for the PC, not for your device. If the app comes from a component supplier and not the OEM, the OEM needs to follow the OEM integration workflow, shown previously, before submitting device metadata. Publishing Device Drivers More information about authoring and validating drivers is available in on MSDN®. Your custom drivers must pass the appropriate Windows Hardware Certification Kit tests before submission. Once the drivers pass, they should be submitted to the so they can be preinstalled. The user shouldn't be required to run any desktop installation program before your device driver is available. Custom drivers should be submitted before your app or device metadata. IMPORTANT Device access using custom drivers requires approval from Microsoft. OEMs and IHVs that want to implement device access for a specialized device using a custom driver should first contact their Microsoft contact to discuss their scenario with the Windows Ecosystem team. For more information see the Custom Driver Access Model section. Because your app needs custom access to a restricted device, when submitting device metadata, you need to choose "This device has associated logo or unclassified submissions …" under Bind to logo submissions. This option requires that you provide the submission ID from the driver submission. This allows the dashboard to verify that the custom drivers have passed the Device.DevFundCDA portion of the Hardware Certification Requirements. Updating a Windows Store Device App for a PC internal specialized device The process for updating a Windows Store device app is very similar to the process for initial deployment. And the unique elements described previously for specialized devices apply in both cases. The components that come together to enable a Windows Store device app for a specialized device are loosely coupled – there's no tight version binding between
The component supplier submits device driver to the Windows Dev Center hardware dashboard for certification and distribution via Windows Update. The OEM passes the (Windows App Certification Kit) (WACK) tests for their app that incorporates functionality from the component supplier. The OEM submits the app to Windows Store. The OEM submits the device metadata package to the Windows Dev Center hardware dashboard for distribution via Windows Metadata and Internet Services The OEM can now preload the certified and digitally signed device driver, device metadata, and app. When submitting a privileged app for a PC internal device for Windows Store download, follow the instructions in , but remember that the metadata in this case is the device metadata package for the PC, not for your device. If the app comes from a component supplier and not the OEM, the OEM needs to follow the OEM integration workflow, shown previously, before submitting device metadata. Publishing Device Drivers More information about authoring and validating drivers is available in on MSDN®. Your custom drivers must pass the appropriate Windows Hardware Certification Kit tests before submission. Once the drivers pass, they should be submitted to the so they can be preinstalled. The user shouldn't be required to run any desktop installation program before your device driver is available. Custom drivers should be submitted before your app or device metadata. IMPORTANT Device access using custom drivers requires approval from Microsoft. OEMs and IHVs that want to implement device access for a specialized device using a custom driver should first contact their Microsoft contact to discuss their scenario with the Windows Ecosystem team. For more information see the Custom Driver Access Model section. Because your app needs custom access to a restricted device, when submitting device metadata, you need to choose "This device has associated logo or unclassified submissions …" under Bind to logo submissions. This option requires that you provide the submission ID from the driver submission. This allows the dashboard to verify that the custom drivers have passed the Device.DevFundCDA portion of the Hardware Certification Requirements. Updating a Windows Store Device App for a PC internal specialized device The process for updating a Windows Store device app is very similar to the process for initial deployment. And the unique elements described previously for specialized devices apply in both cases. The components that come together to enable a Windows Store device app for a specialized device are loosely coupled – there's no tight version binding between
Windows%20Store%20Device%20App%20Design%20Guide%20for%20Specialized%20Devices%20Internal%20to%20the%20PC.docx