Metro style Device App and Metadata Onboarding JOHN

Metro style Device App and Metadata Onboarding JOHN MULLALLY NIKET SANGHVI Program manager

End-to-end onboarding • Create device metadata • Create Metro style device app • Submit device metadata • Confirm download of metadata and installation of app

End-to-end onboarding Reserve app name on the Windows Store Dev Center Decide on monetization options Create device metadata and printer app Ensure device app is live on the Windows Store Submit and publish device app Tightly bind metadata and app using app info and metadata experience ID Submit the device metadata package Check that package is validated and live Confirm proper download and install Windows Store Hardware Dashboard Offline

Metro style device app submission

Establishing your brand § Store Dev Center and Windows Phone App Hub share dev data § If you have a Windows Phone app, sign up to the Windows Dev Center using same Live ID § No need to repeat vetting for company accounts due to shared infrastructure § Account types are Company, Individual § No visible difference to consumers

Submission Design Goals Much more in the Windows Store blog post “Submitting your Windows 8 apps” § Encourage developers to visit the Store developer portal before they start coding § Help developers comply with the Store technical requirements § Reduce concepts and repetition by pulling information directly from the app package

Defining Your App § Setting expectations upfront § Ability to learn more about each option § Scenarios explored on the portal may inspire additional code

Name Reservation § Name uniqueness constraint helps consumers identity apps § Name reservation adds predictability to initial development and testing § Reasonable limits for the number of names a single developer can reserve, and for how long § § High enough that you can have several new projects in development at a time Reserving a name establishes the identity of your app (package name) and provisions your app for services like WNS push notifications, enabling pre-upload testing

Flexible Business Models § Free/ad-supported § In app purchases § Features § Expiring features § 3 rd party commerce systems

Tightly Bind Device Metadata and your App § Device Metadata Experience ID information must be included in Store. Manifest. xml § Store. Manifest. xml must be present in the Metro style device app package <? xml version="1. 0" encoding="utf-8"? > <Store. Manifest xmlns: xsi="http: //www. w 3. org/2001/XMLSchema-instance" xsi: no. Namespace. Schema. Location="Store. Manifest. xsd" xmlns="http: //schemas. microsoft. com/appx/2010/Store. Manifest"> <Product. Features> <Device. Companion. Application> <Experience. Ids> <Experience. Id>F 9 D 916 A 7 -AFD 3 -445 B-8 B 9 C-5 B 6466831 C 9 E</Experience. Id> </Experience. Ids> </Device. Companion. Application> </Product. Features> </Store. Manifest>

Before you Upload § Use Visual Studio to align your local package with Store-assigned details § Enables local testing of push notifications, etc. § Run the Store technical tests locally (Windows App Certification Kit)

Description § One description per app-supported language § Powers the app listing page Optional promotional images may be used to feature app

Release Tracking § Transparency through certification process § More information about each section in the blog post

After Your App is Live § Analytics § Adoption § Usage § Ratings & Reviews § Quality § Preparing an update

Device Metadata Submission

Metadata submission background § Metadata packages are organized into Experiences on the Dashboard § Packages apply to a set of HWIDs and Model. IDs § Packages can be ‘preview’ (for testing) or ‘released’ § Dashboard validates device metadata is functional, follows business policies, and is owned by the submitter § Sends valid packages to Windows Metadata servers for download to Windows computers § Dashboard provides detailed errors for invalid packages § Packages must be signed with the submitting company’s Veri. Sign certificate used to signup

Metadata submissions § Submission process for metadata consistent with Windows 7 § Create an experience, select Logo submission IDs, upload your package(s) to the experience § New features § Multi-locale metadata packages - Must use the devicemanifest-ms package format § Bulk device metadata upload - Supports multiple packages for multiple experiences § Device Metadata Authoring Wizard leverages these new features

Device metadata package § App information must be included in Software. Info. xml § Ensures tight binding between metadata and app

Device metadata package <Device. Companion. Applications> <Package> <Identity Name="microsoft. devx. appx. Hello. World“ Publisher="CN=Microsoft Corporate Root Authority, OU=ITG, O=Microsoft, L=Redmond, S=WA, C=US" /> <Applications> <Application Id="Hello. World. Web. Application" /> </Applications> </Package> </Device. Companion. Applications>

Windows Dev Center – Hardware Dashboard

Create experience

Bind to logo submissions

Manage Experiences

Manage one experience

Multi-locale device metadata packages

Device manifest package § Contains additional information to validate multi-locale packages § § Ensures proper listing in the Device Experience List Multiple locale support § Locale. Info. xml § Specify locale support for proper package validation

Device manifest package § CAB package containing the service metadata package and the extra information

Locale. Info. xml <? xml version="1. 0" encoding="utf-8"? > <Locale. Info xmlns="http: //schemas. microsoft. com/Windows/2010/08/Metadata. Submission/Locale. Info"> <Multiple. Locale>true</Multiple. Locale> <Locale. Declared. In. Package. Info default="true">en-US</Locale. Declared. In. Package. Info> <Supported. Locale. List> <Locale>en-US</Locale> <Locale>ja-JP</Locale> </Supported. Locale. List> </Locale. Info>

Bulk metadata submissions

Bulk metadata package § Contains all information required to submit multiple metadata packages across multiple experiences § Bypasses the submission interface on the Dashboard § Only sign the bulk metadata package, not each individual package § Works with both package types: devicemanifest-ms and devicemetadata-ms

Bulk metadata package § CAB package containing device manifest packages and Bulk. Metadata. Submission. xml

Bulk. Metadata. Submission. xml <? xml version="1. 0" encoding="utf-8"? > <Bulk. Metadata. Submission xmlns="http: //schemas. microsoft. com/Windows/2010/08/Metadata. Submission/Bulk. Metadata. Submission"> <Experience update="false"> <Experience. Name>Printer_Bulk. Submission 1</Experience. Name> <Experience. Id>aaaa-aaaa-aaaaaaaa</Experience. Id> <Package. List> <Package. File. Name preview="true" locale="en-US"> 1111 -1111 -11111111. devicemanifest-ms </Package. File. Name> <Package. File. Name preview=“false" locale="en-US"> 2222 -2222 -22222222. devicemanifest-ms </Package. File. Name> </Package. List> <Qualification>Logo/IDDA</Qualification> </Experience> <Experience update=“false”> … </Experience> </Bulk. Metadata. Submission>

Submission prerequisites § Confirm that your app is live in the Windows Store § Bundle your multi-locale devicemetadata-ms package into a devicemanifest-ms package § You are ready to submit!

Windows Dev Centers

Windows Dev Centers § Use a single Microsoft account across both the Windows App Dev Center and the Windows Hardware Dev Center § § No need to remember multiple usernames and passwords Consistent help documentation and resources to aid with Metro style device apps § Metro style device apps for printers § Preparing your app for the Windows Store § Help with device metadata submissions