Enter app properties

The Properties page of the app submission process is where you define your app's category and enter other info and declarations. Be sure to provide complete and accurate details about your app on this page.

Category, subcategory and secondary category

You must indicate the category (and subcategory/genre, if applicable) which the Store should use to categorize your app. Specifying a category is required in order to submit your app. You can optionally choose a secondary category for your app. Secondary category has the same list of categories as the Primary category.

For more info, see Category and subcategory table.

Support info

This section lets you provide info such as Privacy policy URL, website and support contact info to help customers understand more about your app and how to get support. You are responsible for ensuring your app complies with applicable privacy laws and regulations, and for providing a valid privacy policy URL here if required.

Game settings

This section will only appear if you selected Games as your product’s category. Here you can specify which features your game supports. The information that you provide in this section will be displayed on the product’s Store listing.

If your game supports any of the multiplayer options, be sure to indicate the minimum and maximum number of players for a session. You can't enter more than 1,000 minimum or maximum players.

Cross-platform multiplayer means that the game supports multiplayer sessions between players on Windows 10 or Windows 11 PCs and Xbox.

Display mode

This section lets you indicate whether your product is designed to run in an immersive (not a 2D) view for Windows Mixed Reality on PC and/or HoloLens devices. If you indicate that it is, you'll also need to:

• Select either Minimum hardware or Recommended hardware for Windows Mixed Reality immersive headset in the System requirements section that appears lower on the Properties page.
• Specify the Boundary setup (if PC is selected) so that users know whether it's meant to be used in a seated or standing position only, or whether it allows (or requires) the user to move around while using it.

If you have selected Games as your product's category, you'll see additional options in the Display mode selection that let you indicate whether your product supports 4K resolution video output, High Dynamic Range (HDR) video output, or variable refresh rate displays.

If your product does not support any of these display mode options, leave all of the boxes unchecked.

Product declarations

You can check boxes in this section to indicate if any of the declarations apply to your app. This may affect the way your app is displayed, whether it is offered to certain customers, or how customers can use it.

System requirements

In this section, you have the option to indicate if certain hardware features are required or recommended to run and interact with your app properly.

App properties describe important details about your app including requirements, capabilities, and your contact information. The Properties page of the app submission process is where you define your app's category and enter other info and declarations. Be sure to provide complete and accurate details about your app on this page.

Category, subcategory and secondary category

Category is required

Categories and subcategories help users discover your app, and they help users understand what your app does.

Choose the categories that best describe your app. If the primary category includes subcategories, select the one that best describes your app. If none of the available subcategories seem to fit, you can leave subcategory blank, or choose a subcategory you think customers who would want your app would be most likely to browse. You can optionally choose a secondary category for your app. Secondary category has the same list of categories as the Primary category.

For more info, see Category and subcategory table.

Support info section

This section lets you provide info such as Privacy policy URL, website and support contact info to help customers understand more about your app and how to get support. You are responsible for ensuring your app complies with applicable privacy laws and regulations, and for providing a valid privacy policy URL here if required. You can also provide contact details like Email, Phone number and Address.

Product declarations section

You can check boxes in this section to indicate if any of the declarations apply to your app. This may affect the way your app is displayed, whether it is offered to certain customers, or how customers can use it.

System requirements section

System Requirements (Touch screen, Keyboard, Mouse, Camera, NFC HCE, NFC Proximity, Bluetooth LE, Telephony, Microphone, Memory, DirectX, Dedicated GPU Memory, Processor, Graphics)

When submitting an add-on, the options on the Properties page help determine the behavior of your add-on when offered to customers.

Product type

Your product type is selected when you first create the add-on. The product type you selected is displayed here, but you can't change it.

The fields you see on this page will vary, depending on the product type of your add-on.

Product lifetime

If you selected Durable for your product type, Product lifetime is shown here. The default Product lifetime for a durable add-on is Forever, which means the add-on never expires. If you prefer, you can change the Product lifetime so that the add-on expires after a set duration (with options from 1-365 days).

Quantity

If you selected Store-managed consumable for your product type, Quantity is shown here. You'll need to enter a number between 1 and 1000000. This quantity will be granted to the customer when they acquire your add-on, and the Store will track the balance as the app reports the customer’s consumption of the add-on.

Subscription period

If you selected Subscription for your product type, Subscription period is shown here. Choose an option to specify how frequently a customer will be charged for the subscription. The default option is Monthly, but you can also select 3 months, 6 months, Annually, or 24 months.

Free trial

If you selected Subscription for your product type, Free trial is also shown here. The default option is No free trial. If you prefer, you can let customers use the add-on for free for a set period of time (either 1 week or 1 month).

Content type

Regardless of your add-on's product type, you'll need to indicate the type of content you're offering. For most add-ons, the content type should be Electronic software download. If another option from the list describes your add-on better (for example, if you are offering a music download or an e-book), select that option instead.

These are the possible options for an add-on's content type:

• Electronic software download
• Electronic books
• Electronic magazine single issue
• Electronic newspaper single issue
• Music download
• Music streaming
• Online data storage/services
• Software as a service
• Video download
• Video streaming

Additional properties

These fields are optional for all types of add-ons.

Keywords

You have the option to provide up to ten keywords of up to 30 characters each for each add-on you submit. Your app can then query for add-ons that match these words. This feature lets you build screens in your app that can load add-ons without you having to directly specify the product ID in your app's code. You can then change the add-on's keywords anytime, without having to make code changes in your app or submit the app again.

To query this field, use the StoreProduct.Keywords property in the Windows.Services.Store namespace. (Or, if you're using the Windows.ApplicationModel.Store namespace, use the ProductListing.Keywords property.)

Custom developer data

You can enter up to 3000 characters into the Custom developer data field (formerly called Tag) to provide extra context for your in-app product. Most often, this is in the form of an XML string, but you can enter anything you'd like in this field. Your app can then query this field to read its content (although the app can't edit the data and pass the changes back.)

For example, let’s say you have a game, and you’re selling an add-on which allows the customer to access additional levels. Using the Custom developer data field, the app can query to see which levels are available when a customer owns this add-on. You could adjust the value at any time (in this case, the levels which are included), without having to make code changes in your app or submit the app again, by updating the info in the add-on's Custom developer data field and then publishing an updated submission for the add-on.

To query this field, use the StoreSku.CustomDeveloperData property in the Windows.Services.Store namespace. (Or, if you're using the Windows.ApplicationModel.Store namespace, use the ProductListing.Tag property.)