In this guide
Sources, retrieved 2026-10-22: Microsoft Store Policies, version 7.20 and Apple App Review Guidelines. Microsoft's principles say: "There is no place in our Store for any kind of fraud, be it ratings and review manipulation, credit card fraud or other fraudulent activity." Apple's Guideline 3.2.2(x) says: "Apps must not force users to rate the app, review the app, download other apps, or other store-related actions in order to access functionality, content, or use of the app." I did not verify store rules on the wording or timing of rating prompts; read the current policy of every store you publish in before you add one.
The principles below hold on any platform.
Never buy, swap or reward ratings
Paying for ratings, trading them with other developers, or giving users something in return for a rating all put a rating on your listing that is not an honest opinion. Stores tend to treat this as manipulation, and the risk lands on your developer account. Check each store's current policy. For the full argument, see buy app reviews: risks and what to do instead.
This includes "rate us for a free licence key", discount codes for five stars, and "I'll rate yours if you rate mine".
When to ask
Ask after the user got something done, not at the start and not in the middle of work.
Good moments for a desktop app: - After a task completes successfully, for example a finished export or a saved project. - After the user has come back a few times, so they know the app. - After a problem was solved, such as a support request that ended well.
Bad moments: - On first launch or right after install. - During work, or in the middle of a long process. - Right after an error or crash. - On every start. One ask, then leave them alone for a good while.
The reasoning is the same as on mobile; see when to ask for app reviews.
How to ask
- One sentence, neutral wording: "How is the app working for you?" Do not hint at the answer you want.
- Offer a private route first. If the user is unhappy, send them to a feedback form, not the store page. Do not hide the store option from users who want it.
- Make it easy to dismiss and do not ask again straight after.
- Never promise or give anything for a rating.
Prevent bad ratings at the source
Many desktop one-star ratings come from the install and first launch: security warnings, a missing runtime, an update that lost settings. Test those before release; see testing a Windows installer, update and uninstall and the Windows app testing checklist.
Reply to reviews politely and concretely. If a store lets you respond, a fix with a version number is the best answer.
What AppReviewX covers
AppReviewX accepts apps by store link from Google Play, the Apple App Store, the Mac App Store and the Microsoft Store. Windows and Mac apps must already be published in their store, and AppReviewX does not distribute builds or installers. Feedback is private and structured, one accepted feedback = one credit, and store ratings are voluntary, unpaid and never required. This page is general guidance.
Start free and get private feedback on your app.
Related: Windows and Mac app testing guide, Windows app testing checklist, Mac app testing checklist.