Windows Store quality reports detailed by Microsoft

So you have made a Windows 8 Metro app. You have sent it to Microsoft for their approval and certification and it later appears on the Windows Store. But what happens after that? Microsoft attempts to answer that question with the latest entry on the official Windows Store blog.

Microsoft has set up a way to view quality reports for Windows 8 Metro apps via the Windows Store app summary page. This page offers up information to app makers on issues such as the JavaScript exception rate, the crash rate (as seen in the above screenshot) and the unresponsive app rate. Microsoft states:

The data for calculating the failure rate is collected from a random sample of machines—called a quality panel—on which your app is used. We consider a quality panel of at least 500 machines to be an adequate sample size for calculating the failure rates.

The failure rates are calculated on the basis of the average number of failures during a Windows 8 app's first 15 minutes of active usage. Microsoft also provides a list of the top five most common failures for a Windows 8 app. Developers can download a .cab file for each failure. Microsoft says, "The .cab file contains a process dump associated with the failure in your app. You can get the stack traces and other details for the failure from the process dump."

The blog goes into a lot of technical detail of how Windows 8 Metro app creators can process the .cab files to find out what went wrong with their app so they can fix it and release and updated version. Microsoft adds:

We believe that understanding and improving quality is critical to building a successful app. We have designed the quality reports to provide you useful and actionable data to improve your app. We are confident that these reports will help you prioritize improvements and deliver quick updates to your apps in the Store.

Source: Windows Store blog | Image via Microsoft

Previous Story
Interview: We get more info about MechWarrior Tactics
Next Story
iTunes could get a big overhaul by end of 2012