Create your app info

Whether you're submitting an app for the first time—creating an app—or just looking to make an improvement—updating an existing app—the Windows Phone Dev Center empowers you to submit your apps simply and efficiently. Use this guide to help you create or update the necessary info for your app before submitting it for approval.

The App info page is used to refer to your app in the Dev Center, and also controls how it appears in the Windows Phone Store. Give your app a Dev Center alias, associate it with your Windows version, price it, and enter other relevant info.

Associate your Windows Phone and Windows Store apps

Your Windows Phone app can share an identity in the Windows Phone Store and the Windows Store. This means that a customer who purchased your app in either store can download the app from the other Store without paying for it again, and your app can roam data between Windows Phone and Windows. Check out the See Also links at the end of this topic to learn more about in-app purchases, roaming data, and the Windows Push Notification Service.

Important noteImportant Note:

If you plan to associate your Windows Phone app with a Windows app and your apps offer in-app products, your in-app products that share an alias in the Windows and Windows Phone stores also must share the same type, Consumable or Durable, for example. See In-app product properties for more information.

Your app’s identity is assigned when you reserve a name for the app on either the Windows Phone Dashboard, the Windows Store Dashboard, or Visual Studio. If you’ve already reserved a name for your app and you want to share an identity between Windows Phone and Windows, choose that name. If you haven’t reserved a name for this app yet or you don’t want your app to share an identity between the two stores, reserve a new name for it. Any name you reserve also is reserved for you in the Windows Store.

After you reserve a name, you must submit the app for certification within one year or you will lose your name reservation.

Your beta app and public app can’t have the same package identity.

Important noteImportant Note:

After you associate your Windows Phone Store app with your Windows Store app and submit the update, the association cannot be reversed or deleted. Also, your Windows Phone app will map exactly to your Windows Store app.

Reserve your app names

Windows Phone apps leverage the name reservation system used by Windows Store to share the same unique app names across both stores. You must reserve a new unique app name, or reuse a name already reserved for your companion Windows Store app, for your new Windows Phone app or updated Windows Phone 8.1 version of your existing Windows Phone app. App names reserved in one store are automatically available for the app to use in the other store. Similarly, releasing an app name from one store releases it from the other store. An app name can be released only if neither store has a currently submitted package using the name. You will get an error during submission if your app package contains unreserved app names or names that haven’t been used in previously published versions.


A Windows Phone app that is already published can continue to use the same app title, even if you add a Windows Phone 8.1 package to it or associate it with a Windows Store app.

App associating scenarios


Clearly defining your app's identity when choosing a category and subcategory can help users find it more easily in the Store. If you feel your app belongs in a different category after you submit it, don’t worry. You can change it at any time. Note that some categories will have subcategories. If you select a category that has a subcategory, you must assign a subcategory in order to submit the app. If you’re new to developing for Windows Phone or are unfamiliar with the Store categories, see Category table.

You can change the price of your app in the Dev Center at any time before, during, or after certification. If your app is free, select $0.00 in the price list. If you are selling paid apps, learn more about Base price and setting custom prices on a country-by-country basis in Define pricing and market selection.


Select the Offer free trials of this app check box if you plan to offer a trial version of your app. If you want to put a trial app on the Store, you must use the Trial API to implement different or limited functionality for the trial version. To learn more about making trial apps, see Creating trial apps for Windows Phone 8.

After setting your app's price, you'll need to determine its distribution model and select the markets where you'd like to sell it. Your distribution choices are:

  • Distribute to all markets at the base tier  This is the default form of app distribution. This selection attempts to publish to all countries or regions currently supported by Windows Phone Store.

  • Distribute to all markets except China  Content that is offensive in any country/region to which your app is targeted is not allowed. Content may be considered offensive in certain countries/regions because of local laws or cultural norms. China has some unique restrictions on app content. For more information, see section 3.10 in Content policies for Windows Phone.

  • Continue distributing to current markets  Select this option if you plan to customize your market pricing or if you’re updating your app and prefer to keep your app’s existing market settings.

Remember, you must submit your payment and tax info during Registration or in the Account section of your Dev Center Dashboard before you can submit paid apps. After you’ve made your App Details and Pricing selections, you can either Save and proceed to Step 2, Upload and describe your package(s), or continue modifying App Info in the More options area.

In the More options list, you can customize the distribution and publishing parameters that make the most sense for your app.

Distribution channels

Where do you want your app to go—directly into the Store, or into beta testing? If you choose beta testing, tell us in the box who'll be trying out your app (beta tester email addresses only). Your testers will need to have Microsoft accounts (formerly called Windows Live accounts) to try out your app. To learn more, see Beta testing your app and in-app products.


Windows Phone public and beta apps can’t share the same package identity name. Don’t associate a Windows Phone beta app with a published Windows Store app because it would make the Windows Store app become available as a free download because Windows Phone beta apps are free.


How will your app go live—automatically or manually? Select Automatically, as soon as it’s certified if you want your app in the Store as soon as possible. When publishing automatically in the Public Store, expect to see your app in five to seven business days after successful submission. Go with Manually, at any time after it’s certified if you’d like to control the timing of the release yourself. If you make no adjustments in the More options list, Public Store and Automatically, as soon as it’s certified are set as the default distribution and publishing selections for your app.

Push notifications

If you've got an app in the Store and you've just submitted an update, authenticated push notifications are a great way to tell current users about the improvements you’ve made. Learn more about Push notifications for Windows Phone 8 and Windows Push Notification Service (WNS).

Game rating certificates

For apps published in the games category, you can upload certificates you’ve acquired from rating agencies. Some countries or regions require a specific version of the certificate awarded by the agency. The game will not be offered automatically in countries or regions where game rating certificates are required. Learn more about Game ratings.

When you've filled out your app info and you're satisfied with the changes, click Save. If your save action is successful, you'll be redirected to the Submit app or Update app page, where you’ll see a check box next to App info. You're now ready to proceed to the next step, Upload and describe your package(s).

If you need help with errors, see Understanding app submission errors.

© 2015 Microsoft