Update Add-ons documentation (Submit your app) #5465
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@luislera : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
prmerger-automator
bot
added
apps/subsvc
Change sent to author
windows-app-sdk/svc
labels
|
Learn Build status updates of commit 7648bef:
|
PRMerger Results
|
|
|
||
| You must provide a description, up to 200 characters. This information will be displayed to customers along with the title. | ||
|
|
||
| ### Icon |
There was a problem hiding this comment.
I like that we have added this. Why have we excluded the other parameters like what's new, etc.?
There was a problem hiding this comment.
The only fields available for updating store listings are the following:
What do you mean with parameters like what's new, etc.?
| | **Icon** | Optional (.png, 300x300 pixels) | | ||
|
|
||
| When you've finished entering this info, click **Submit to the Store**. In most cases, the certification process takes about an hour. After that, your add-on will be published to the Store and ready for customers to purchase. | ||
|
|
||
| > [!NOTE] | ||
| > The add-on must also be implemented in your app's code. For more info, see [In-app purchases and trials](/windows/uwp/monetize/in-app-purchases-and-trials). | ||
|
|
||
| ## Set your add-on product type and product ID | ||
|
|
||
| An add-on must be associated with an app that you've created in Partner Center (even if you haven't submitted it yet). You can find the button to Create a new add-on on your app's Overview page or on its Add-ons page. |
There was a problem hiding this comment.
Why have we removed this?
There was a problem hiding this comment.
The same content is included at the beginning of this document
Is that ok to remove the duplicated text?
| @@ -47,7 +47,7 @@ Review this list to help avoid issues that frequently prevent apps from getting | |||
|
|
|||
| - [Provide any necessary info](./manage-submission-options.md#notes-for-certification) required to use your app, such as the user name and password for a test account if your app requires users to log in to a service, or any steps required to access hidden or locked features. | |||
|
|
|||
| - Include a [privacy policy URL](./support-info.md#privacy-policy-url) if your app requires one; for example, if your app accesses any kind of personal information in any way or is otherwise required by law. To help determine if your app requires a privacy policy, review the [App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905) and the [Microsoft Store Policies](../../store-policies.md). | |||
| - Include a [privacy policy URL](./enter-app-properties.md#privacy-policy-url) if your app requires one; for example, if your app accesses any kind of personal information in any way or is otherwise required by law. To help determine if your app requires a privacy policy, review the [App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905) and the [Microsoft Store Policies](../../store-policies.md). | |||
|
|
|||
| - Make sure that your app's description clearly represents what your app does. For help, see our guidance on [writing a great app description](./write-great-app-description.md). | |||
There was a problem hiding this comment.
Can we refer to Write a great app description in best practices section?
There was a problem hiding this comment.
I've added the link to best practices section.
There was a problem hiding this comment.
Where is the content from this file added?
There was a problem hiding this comment.
It was included in the Add properties section. We made this change to ensure the documentation matches the order of the Add-on properties fields, providing a more consistent and user-friendly experience.
There was a problem hiding this comment.
Should we have one article on great app description in best practices section. Anything that applies to add-ons can be mentioned separately on the page?
There was a problem hiding this comment.
As far as we checked, the content of this section is the same as the one added in best practices section. Should we remove this document?
|
Learn Build status updates of commit d948534: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
Learn Build status updates of commit 3992774: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
Learn Build status updates of commit cc98816:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| hub/apps/publish/publish-your-app/add-on/app-certification-process.md | Details | ||
| hub/apps/publish/publish-your-app/add-on/manage-submission-options.md | Details | ||
| hub/apps/publish/publish-your-app/add-on/price-and-availability.md | Details | ||
| hub/apps/publish/publish-your-app/add-on/visibility-options.md | Details | ||
| hub/apps/publish/best-practices/best-practices.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/add-on/add-and-edit-store-listing-info.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/publish-your-app/add-on/configure-release-schedule.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/add-on/create-app-store-listing.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/add-on/create-app-submission.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/add-on/enter-app-properties.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/add-on/market-selection.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/add-on/product-declarations.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/add-on/publish-update-to-your-app-on-store.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/add-on/reserve-your-apps-name.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/add-on/resolve-submission-errors.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/add-on/schedule-pricing-changes.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/add-on/support-info.md | ✅Succeeded | n/a (file deleted or renamed) | |
| hub/apps/publish/publish-your-app/add-on/what-are-add-ons.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/add-on/write-great-app-description.md | ✅Succeeded | ||
| hub/apps/publish/publish-your-app/msix/images/msix-set-app-pricing-other-types.png | ✅Succeeded | ||
| hub/apps/publish/toc.yml | ✅Succeeded |
hub/apps/publish/publish-your-app/add-on/app-certification-process.md
- Line 32, Column 99: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#configure-precise-release-scheduling' in 'apps/publish/publish-your-app/add-on/schedule-pricing-changes.md'.
hub/apps/publish/publish-your-app/add-on/manage-submission-options.md
- Line 15, Column 117: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#configure-precise-release-scheduling' in 'apps/publish/publish-your-app/add-on/schedule-pricing-changes.md'. - Line 19, Column 283: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#configure-precise-release-scheduling' in 'apps/publish/publish-your-app/add-on/schedule-pricing-changes.md'.
hub/apps/publish/publish-your-app/add-on/price-and-availability.md
- Line 36, Column 20: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#configure-precise-release-scheduling' in 'apps/publish/publish-your-app/add-on/schedule-pricing-changes.md'.
hub/apps/publish/publish-your-app/add-on/visibility-options.md
- Line 36, Column 249: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#configure-precise-release-scheduling' in 'apps/publish/publish-your-app/add-on/schedule-pricing-changes.md'. - Line 46, Column 24: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#configure-precise-release-scheduling' in 'apps/publish/publish-your-app/add-on/schedule-pricing-changes.md'.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
|
Learn Build status updates of commit 2386472: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
learn-build-service-prod bot
added a commit
that referenced
this pull request
Jun 6, 2025
…c_temp For protected branch, push strategy should use PR and merge to target branch method to work around git push error
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes included