Quickly build Windows 8 style Apps 37-Common publishing considerations

Original: Quick build Windows 8 style Apps 37-Common publishing considerations

Introduction

Usually after we publish the Windows Store app fails, we will return some errors that we need to modify. When I was doing training for students, I found that most of the students were beaten back, usually by the following common reasons:

1, Privacy policy;

2, apply icons and text;

3, localization;

In order to avoid these three causes of application publishing failure, we develop the application of how to pay attention to and effectively avoid it?

First, Privacy Policy

1. Add a scenario for Privacy Policy (extract MSDN)

• Collection of personal information or use of software provided by others, you will need to provide a privacy policy or other license terms with your app.
• When you need to get or write data from the network in your app, you'll need to provide a privacy policy or other license terms with your app.

2. Add Privacy Policy-Settings panel

1) Open the NuGet package for the management solution

2) Import the Callisto application package;

3) Open the App.xaml.cs file in the application solution. Add a namespace.

using Windows.ui;

using Windows.UI.ApplicationSettings;

using Callisto.controls;

The commandsrequested event is registered in the Onlaunched method.

Settingspane.getforcurrentview (). commandsrequested + = app_commandsrequested;

4) Show privacy Policy in "Setup Panel"

void App_commandsrequested (settingspane sender, Settingspanecommandsrequestedeventargs args)

{

    New Settingscommand ("Privacypolocyid", "Privacy Policy", (handler) =

    {

        New Settingsflyout ();

        The Content property shows the app privacy policy

        "The purpose of this privacy policy is to explain when you access and use XX apps" "\ n" "and the information we may collect about the services," "\ n" "How will we use this information and whether it will be disclosed to third parties," "\ n" "and your choice of the use and modification of these materials. This privacy policy applies to the XX application,"\ n"does not apply to other non-XX products. You need to carefully read the privacy policy of the product itself. ";

        "Privacy Policy";

        New SolidColorBrush (Color.FromArgb (255, 0, 77, 96));

        New SolidColorBrush (Color.FromArgb (255, 0, 77, 96));

        true;

     });

     Args. REQUEST.APPLICATIONCOMMANDS.ADD (Privacypolocy);

}

5) display effect, "Launch Application", "Select settings in the Charms button, pop up the Settings panel", click "Privacy Policy" to view privacy policy information "

3, add privacy Policy-point to URL

1) point to a URL to browse privacy policy information

void App_commandsrequested (settingspane sender, Settingspanecommandsrequestedeventargs args)

{

   New Settingscommand ("Privacypolocyid", "Privacy Policy", (handler) =

   {

      var isseccess = Windows.System.Launcher.LaunchUriAsync (Thenew Uri ("Http://www.cnblogs.com/wzk89/articles /2718356.html "));

   });

   Args. REQUEST.APPLICATIONCOMMANDS.ADD (Privacypolocy);

}

2) View Run effect

4. Add Privacy Policy-App Store submission

The App Store submits the "Feeds" section of the app's privacy policy.

5, no privacy policy is required

• If data is not acquired or read and written from the network in the app, the app does not need to provide a privacy policy.
• You need to uncheck the Internet entry for the Capabilities tab in the app manifest file.

Second, apply the icon and text

You need to create your own app's icon in accordance with the specified picture resolution and format, and replace the icon that is generated by default in your app.

1,package.appxmanifest Application UI

• Logo.png Resolution: 150*150;
• Smalllogo.png Resolution: 30*30;
• Splashscreen.png Resolution: 620*300;

2,package.appxmanifest Packaging

• Storelogo.png Resolution: 50*50;

You need to modify the application's default naming and description based on the functionality of your application.

1,package.appxmanifest Application UI

• Display name modification;
• Description modification;
• Short name modification;

2,package.appxmanifest Packaging

• Package Display name modification;

Third, localization

1, page localization: Because we choose the market is the Chinese market, so all the application of the page must be Chinese, can not appear in third-party languages such as English, Japanese and so on.

2, screenshot localization: All screenshots The same reason can not appear in addition to Chinese third-party language (if we choose to publish the market is China).

Note: regarding the localization audit, in the age choice under 12 years of age is especially strict, so the proposal generally changes to 12+ above.

Quickly build Windows 8 style Apps 37-Common publishing considerations