1 / 35

Metro style Device App and Metadata Onboarding

Metro style Device App and Metadata Onboarding. John mullally Niket sanghvi. Program manager Program manager. End-to-end onboarding. Create device metadata Create Metro style device app. Submit Metro style device app. Submit device metadata.

tekla
Download Presentation

Metro style Device App and Metadata Onboarding

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Metro style Device App and Metadata Onboarding John mullally Niket sanghvi Program manager Program manager

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

  3. Windows Store End-to-end onboarding • Hardware Dashboard Offline

  4. Metro style device app submission

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

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

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

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

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

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

  11. 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)

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

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

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

  15. Device Metadata Submission

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

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

  18. Device metadata package App information must be included in SoftwareInfo.xml Ensures tight binding between metadata and app

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

  20. Windows Dev Center – Hardware Dashboard

  21. Create experience

  22. Bind to logo submissions

  23. Manage Experiences

  24. Manage one experience

  25. Multi-locale device metadata packages

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

  27. Device manifest package CAB package containing the service metadata package and the extra information

  28. LocaleInfo.xml • <?xml version="1.0" encoding="utf-8"?> • <LocaleInfoxmlns="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>

  29. Bulk metadata submissions

  30. 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-msand devicemetadata-ms

  31. Bulk metadata package CAB package containing device manifest packages and BulkMetadataSubmission.xml

  32. BulkMetadataSubmission.xml <?xml version="1.0" encoding="utf-8"?> <BulkMetadataSubmissionxmlns="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>

  33. 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!

  34. Windows Dev Centers

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

More Related