Nothing is more frustrating than working on a great new app, submitting it to the app store for approval and receiving a rejection notice. What did you do wrong? Why was your app rejected? You likely got an explanation with the rejection notice, but it might be vague and unhelpful. You can scour the web for best practices, but what better place to get app development do’s and don’ts than straight from the people responsible for approving or rejecting your app?
A recent post on the Windows Phone Developer Blog gathered members of the Windows Phone Store Certification and Policy team to share the most common reasons Windows Phone apps are rejected. Here are the top seven reasons apps are rejected (from most common to least common).
Incorrect app screenshots
Your app screenshots should not include any emulator chrome, frame rate counters, or debug information. They should not be altered or be transparent. Also, photos of your app running on a device or the emulator are not substitutes for a screenshot taken with the emulator.
Missing information to test the app
Many apps require login credentials to run. If your app requires an existing account, make sure you create a test account that can be used by the certification team during testing. Don’t forget to include the account credentials in the Certification notes in your Dev Center submission.
This requirement is simply to verify that your app doesn’t crash during certification testing. As you know, if your app crashes in release mode, it just goes away without any user prompt. Certification will reject your app if it “unexpectedly terminates” during testing.
Incorrect icons and tile images
Developers sometimes forget to replace default icons and tile images in an app created from a Visual Studio template.
Incorrect use of the Back button
The Back button behavior is narrowly defined. The Back button should:
– Close the app only if the app is on the main page
– Go to the previous page only if not on the main page
– Close an open dialog
– Close the soft keyboard
Insufficient localization information
For each of the languages your app supports, you must provide a localized app description. This is the description entered as part of your Dev Center submission. Certification testing also verifies that your app displays properly for each of the languages your app supports.
Lack of support for both light and dark phone themes
This requirement ensures your app displays properly in both light and dark themes. You can switch between themes on your phone.
These mistakes touch on a few key areas, from simple attention to detail and testing usability on a Windows Phone with someone who is familiar with the OS’s UI standards to understanding the importance of thorough localization testing and being able to collect in-depth crash reports while testing your app.
For tips on avoiding these common mistakes, read the Windows Phone Developer Blog >>>