Provide a name for your desktop app
The name that appears here for your desktop app is taken directly from your Windows App Certification Kit submission. You have two options for completing this step:
You can submit your app to the Windows Store with a unique name.
You can reuse an app name from one of your Windows Store listings (a listing you submitted for Windows 8), and add Windows 8.1 info to that listing.
If you are reserving an app for which you’d like to use a new, unique app name for Windows 8.1, you can reserve only one name per app. Edit this name in the field provided, and click Reserve app name to reserve it in the Windows Store. You can also edit this name at any time later, when you create a new release of your app in the Windows Store.
Apps in the Windows Store must have unique names, and we check for uniqueness across all apps in the Windows Store. If you would like to list multiple versions of your app in the Windows Store, we recommend that you append the version number to your app name. This way, you can avoid a naming conflict in the Windows Store, and users will be able to easily find both versions of your app at once. If the language versions of your app have different names, you must run and submit the Windows App Certification Kit separately for these apps, and they must also be submitted and listed separately in the Windows Store.
If you would like to reuse an app name, you can use the drop-down list to associate your new app with one of your existing listings. This works only if you have already listed an app in the Windows Store for Windows 8 and would like to reuse that app name for your Windows 8.1 app.
Select your app from the drop-down list. Once you have selected an app name, one of the buttons below the drop-down list then appears in blue to guide you through completing the association. This can be a two-step process (using both Create and Associate options) if the app you are associating with does not already have a release in the Windows Store. However, if a new release has already been created and is pending, this is a one-step process. In short, a new release must first be created, and then the association can be made.
There are some limits to what you can associate during this step. App releases that are currently in the process of Windows Store certification can't be associated, and you'll see a warning message if you try this. Also, you can't associate an antimalware app with a non-antimalware app. This restriction helps ensure that apps are listed correctly in the Security & PC Protection category.
Build date: 11/16/2013