Skip to content

Commit fe05700

Browse files
Merge pull request #5427 from MicrosoftDocs/ipsitac-StoreBuildUpdates2025
Ipsitac store build updates2025
2 parents 7615fc8 + a30840c commit fe05700

File tree

2 files changed

+68
-0
lines changed

2 files changed

+68
-0
lines changed
Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
description: What’s new - Improved Health Report in Partner Center
3+
title: What’s new - Improved Health Report in Partner Center
4+
ms.date: 05/16/2025
5+
ms.topic: article
6+
keywords: windows 10, windows 11, windows, windows store, store, analytics, health, crash, failure, hang, stack trace
7+
ms.localizationpriority: medium
8+
---
9+
10+
# What’s new: Improved Health Report in Partner Center
11+
12+
> [!IMPORTANT]
13+
> Improved Health report will be coming soon for all MSIX apps and games.
14+
15+
Quality is essential to the success of your app or game on Microsoft Store. To help you monitor and address quality issues more effectively, we will be introducing significant updates to the Health report in Partner Center.
16+
These enhancements are designed to make it easier to identify and analyse failures impacting your customers.
17+
18+
### Redesigned dashboard focused on key metrics
19+
20+
The updated dashboard will bring the most important information to the forefront with key metrics being displayed at the top of the page, making it easier to track quality at a glance.
21+
In the sections below the main dashboard, you’ll find additional metrics and trends over time. You will also be able to compare how your quality metrics evolve with each app update, helping you identify performance improvements or regressions.
22+
23+
### New quality metrics
24+
25+
To provide better visibility into customer impact, we’re introducing following new metrics:
26+
27+
#### Devices affected
28+
This metric will show the number of unique devices per day experiencing crashes, hangs, or other failures like memory failures. If multiple failures occur on the same device in a single day, it will be counted as one device—helping you gauge the breadth of the issue across your user base.
29+
30+
#### Crash rate
31+
The crash rate metric will represent the percentage of daily unique devices that experienced at least one crash. It is calculated by taking the number of unique devices affected by crash divided by the total number of active devices that day. This metric is calculated based on the data collected from devices who have opted in to share optional diagnostic data.
32+
33+
#### Hang rate
34+
Similar to crash rate, the hang rate metric will indicate the percentage of daily unique devices that experienced at least one hang (when app or game is unresponsiveness). This is also calculated using data from devices that have opted in to share optional diagnostic data.
35+
36+
Together, crash rate and hang rate metrics will help you understand the severity of failures affecting your customers.
37+
38+
### New tools for deeper analysis
39+
To help you investigate and resolve issues more efficiently, we’ve added several new tools to the Health report:
40+
41+
#### New visualization for comparison by app version
42+
You can now compare failure metrics across different versions of your app to track if there are any performance improvements or regressions between releases. You can also compare your failure metrics across different architecture and operating system to detect patterns and identify the root causes of issues faster.
43+
44+
#### Multi-filter support
45+
We are now supporting using multiple filters simultaneously. Developers can now apply multiple filters simultaneously—such as multiple app version, OS versions, device types and more, allowing for more precise & targeted analysis.
46+
47+
### Proactive email alerts
48+
To keep you informed, we’re going to introduce email notifications when significant spikes are identified for your quality metrics. These alerts help you catch emerging issues early, so you can act quickly to minimize impact on your users.

hub/apps/publish/last-update-date.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
description: What’s new - Last Updated Date in Microsoft Store
3+
title: What’s new - Last Updated Date in Microsoft Store
4+
ms.date: 05/16/2025
5+
ms.topic: article
6+
keywords: windows 10, windows 11, windows, windows store, store, update date, release date
7+
ms.localizationpriority: medium
8+
---
9+
10+
# What’s new: Last Updated Date in Microsoft Store
11+
12+
> [!IMPORTANT]
13+
> Last Updated Date in Microsoft Store is coming soon for all MSIX & Win32 products.
14+
15+
Microsoft Store will now display the Last updated date on your product page, giving customers greater visibility into your product’s maintenance and release cadence.
16+
This date will reflect when your most recent package update became available to all Microsoft Store users.
17+
18+
The Last updated date will be shown for package updates going forward. As developers start making regular updates on Store, this date will automatically appear in the Additional info section of the product page. This will give potential users insight into whether an app is actively maintained. This added transparency will help users make more informed decisions and will give developer a simple way to showcase their ongoing commitment to app quality.
19+
20+
Regularly updated apps are more likely to be installed by Windows users. So, keep your app fresh, and let your updates work harder for your discoverability.

0 commit comments

Comments
 (0)