11 out of 15 rated this helpful - Rate this topic

Avoiding common certification failures

Review this list to help avoid issues that frequently prevent apps from getting certified.

Note  If your app fails certification for a reason not listed here, check out Resolving certification errors.

  • Submit your app only when it's finished. If your app contains incomplete sections, links to webpages that are under construction, or anything else that would give a customer the impression that your app is incomplete, it is likely to fail certification. (See certification requirement 1.2 for more info.)

  • Test your app with the Windows App Certification Kit before you submit your app.

  • Test your app on several different platforms to ensure that it's as stable as possible. (See certification requirement 3.2 for more info.)

  • Make your app's description as detailed as possible so that it clearly represents what your app does. For help, see our guidance on writing a great app description. (See certification requirement 6.5 for more info.)

  • Don't use your app's listing page to promote your company or other products. (See certification requirement 2.3 for more info.)

  • You're welcome to use your app's description to mention upcoming features. However, if the list of upcoming features give the impression that your app is incomplete, it is likely to fail certification. (Again, see certification requirement 1.2 for more info.)

  • If your app connects to a network, you must include a privacy statement in your app's metadata. Customers must be able to access the privacy statement from the Settings charm when they open your app.. You must also provide access to your privacy policy in your app's listing. (See certification requirement 4.1 for more info.)

  • Most apps should have a rating of 12+, unless they are specifically intended for a younger audience. If you're having trouble deciding between two age ratings for your app, choose the higher one. Remember that apps never fail certification for having too high a rating. (See certification requirement 6.2 for more info.)

  • If you have localized your app, be consistent with localization and make sure your screen shots demonstrate that you've localized your app. (Keep in mind that languages are not the same as markets.) See globalizing your app for more help.

  • If your app uses the Windows Store commerce APIs from the Windows.ApplicationModel.Store namespace, make sure to test the app and verify that it handles typical exceptions. Also, make sure that your app uses the CurrentApp class (not the CurrentAppSimulator class, which is for testing purposes only).

  • Make sure that your app doesn't crash without network connectivity. Even if a connection is required to actually use your app, it needs to perform appropriately when no connection is present.

  • Don't declare your app as accessible unless you have specifically engineered and tested it for accessibility scenarios.

  • Make sure that you provide any necessary info 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.

 

 

Build date: 3/26/2013

© 2013 Microsoft. All rights reserved.