Metro style Device App and Metadata Onboarding

JOHN MULLALLY NIKET SANGHVI

Program manager Program manager

• Create device metadata• Create Metro style device app

• Submit Metro style device app

• Submit device metadata

• Confirm download of metadata and installation of app

End-to-end onboarding

End-to-end onboarding

Reserve app name on the Windows Store Dev Center

Decide on monetization

options

Create device metadata and

printer app

Tightly bind metadata and app using app info and

metadata experience ID

Submit and publish device app

Ensure device app is live on the

Windows Store

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

3rd party commerce systems

Tightly Bind Device Metadata and your App

Device Metadata Experience ID information must be included in StoreManifest.xml

StoreManifest.xml must be present in the Metro style device app package

<?xml version="1.0" encoding="utf-8"?><StoreManifest   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  xsi:noNamespaceSchemaLocation="StoreManifest.xsd"   xmlns="http://schemas.microsoft.com/appx/2010/StoreManifest">  <ProductFeatures>    <DeviceCompanionApplication>      <ExperienceIds>        <ExperienceId>F9D916A7-AFD3-445B-8B9C-5B6466831C9E</ExperienceId>      </ExperienceIds>    </DeviceCompanionApplication> </ProductFeatures></StoreManifest>

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 ModelIDs

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 VeriSign 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 SoftwareInfo.xml

Ensures tight binding between metadata and app

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

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

LocaleInfo.xml

Specify locale support for proper package validation

Device manifest package

CAB package containing the service metadata package and the extra

information

LocaleInfo.xml<?xml version="1.0" encoding="utf-8"?>

<LocaleInfo xmlns="http://schemas.microsoft.com/Windows/2010/08/MetadataSubmission/LocaleInfo">

<MultipleLocale>true</MultipleLocale>

<LocaleDeclaredInPackageInfo default="true">en-US</LocaleDeclaredInPackageInfo>

<SupportedLocaleList>

<Locale>en-US</Locale>

<Locale>ja-JP</Locale>

</SupportedLocaleList>

</LocaleInfo>

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

BulkMetadataSubmission.xml

BulkMetadataSubmission.xml<?xml version="1.0" encoding="utf-8"?>

<BulkMetadataSubmission xmlns="http://schemas.microsoft.com/Windows/2010/08/MetadataSubmission/BulkMetadataSubmission">

<Experience update="false">

<ExperienceName>Printer_BulkSubmission1</ExperienceName>

<ExperienceId>aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa</ExperienceId>

<PackageList>

<PackageFileName preview="true" locale="en-US">

11111111-1111-1111-1111-111111111111.devicemanifest-ms

</PackageFileName>

<PackageFileName preview=“false" locale="en-US">

22222222-2222-2222-2222-222222222222.devicemanifest-ms

</PackageFileName>

</PackageList>

<Qualification>Logo/IDDA</Qualification>

</Experience>

<Experience update=“false”> … </Experience>

</BulkMetadataSubmission>

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