You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add PWA as first-class distribution path in decision guide (#6664)
* Add PWA as first-class distribution path in decision guide
- Add NOTE callout at top routing web app developers to PWA section
- Add PWA row to the distribution paths comparison table
- Add 'Progressive Web App (PWA)' section with what you get,
requirements, limitations, and when to choose PWA vs native
- Cross-link to PWABuilder, Edge PWA docs, and Store submission
- Add PWA to Related content links
Closes P2-4 from Indie Dev Doc Plan Round 2 (04/20/2026).
Co-authored-by: Copilot <[email protected]>
* Address Copilot feedback: fix PWA description metadata, table consistency, PWA wording, MSIX sideloading heading
- Update front-matter description to include PWA
- Fix 'Via Intune' -> 'Via Intune with Company Portal' in table for consistency
- Fix 'No MSIX tooling required' -> 'No manual MSIX authoring required' (Store-published PWAs are still packaged, just auto-generated by PWABuilder)
- Re-add missing '## MSIX sideloading — enterprise LOB distribution' heading
Co-authored-by: Copilot <[email protected]>
---------
Co-authored-by: Copilot <[email protected]>
Copy file name to clipboardExpand all lines: hub/apps/package-and-deploy/choose-distribution-path.md
+36-2Lines changed: 36 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
---
2
2
title: Choose a distribution path for your Windows app
3
-
description: Compare the available Windows app distribution paths — Microsoft Store, MSIX sideloading, and direct download — to find the right fit for your app and audience.
3
+
description: Compare the available Windows app distribution paths — Microsoft Store, PWA, MSIX sideloading, and direct download — to find the right fit for your app and audience.
4
4
ms.topic: concept-article
5
-
ms.date: 04/17/2026
5
+
ms.date: 04/20/2026
6
6
ms.localizationpriority: medium
7
7
---
8
8
@@ -13,11 +13,15 @@ How you distribute your Windows app affects code signing costs, update mechanics
13
13
> [!TIP]
14
14
> **For most developers, the Microsoft Store is the recommended path.** It provides free code signing, built-in update delivery, broad discoverability, and a trusted install experience — with no infrastructure to manage.
15
15
16
+
> [!NOTE]
17
+
> **If your app is built on web technologies** (HTML, JavaScript, CSS), a [Progressive Web App (PWA)](#progressive-web-app-pwa) is the fastest path to the Microsoft Store — no native packaging tools required.
18
+
16
19
## Distribution paths at a glance
17
20
18
21
| Path | Best for | Code signing cost | Auto-update | Enterprise MDM | Distributed via Store |
19
22
|---|---|---|---|---|---|
20
23
|**Microsoft Store**| Consumer and business apps, broad reach | ✅ Free (Store signs for you) | ✅ Built-in | ✅ Via Intune with Company Portal | ✅ Yes |
24
+
|**PWA (Progressive Web App)**| Web apps and web-based experiences | ✅ Free (Store signs for you) | ✅ Via Store or browser | ✅ Via Intune with Company Portal | ✅ Yes |
21
25
|**MSIX sideload (enterprise)**| Internal LOB apps via Intune/ConfigMgr | 💲 Azure Artifact Signing (formerly Trusted Signing) (~$10/mo) or self-signed + Intune cert profile | ✅ Via App Installer file or MDM | ✅ Native | ❌ No |
22
26
|**MSIX direct download (ISV)**| Commercial apps sold from your own site | 💲 CA-trusted cert required ([Azure Artifact Signing (formerly Trusted Signing)](/azure/trusted-signing/) recommended) | ✅ Via `.appinstaller` file | ⚠️ Limited | ❌ No |
23
27
|**Packaging with external location**| Existing apps with own installer needing Windows features | 💲 Same as MSIX direct download | ✅ Your existing mechanism | ⚠️ Limited | ❌ No |
@@ -45,6 +49,35 @@ Publishing to the Microsoft Store is the most complete distribution solution for
45
49
46
50
→ [Publish to the Microsoft Store](/windows/apps/publish/publish-your-app/msix/create-app-submission)
47
51
52
+
## Progressive Web App (PWA)
53
+
54
+
If your app is a website or built primarily on web technologies, a Progressive Web App is the fastest path to the Microsoft Store — with no native packaging tools or code signing purchase required.
55
+
56
+
A PWA is a web app that browsers can install as a standalone app. It can run offline, send push notifications, appear in the Start menu and taskbar, and be distributed through the Microsoft Store. Use [PWABuilder](https://www.pwabuilder.com/) to package your site for Store submission in minutes.
57
+
58
+
**What you get:**
59
+
- Store distribution with free code signing (Store signs the package)
60
+
- Works across any device with a modern browser
61
+
- No manual MSIX, WiX, or installer authoring required — tools like [PWABuilder](https://www.pwabuilder.com/) generate the Store submission package for you
62
+
- Built-in update delivery — users always get your latest web content (hosted content updates without a Store re-submission)
63
+
64
+
**Requirements:**
65
+
- App must be served over HTTPS
66
+
- A [web app manifest](https://developer.mozilla.org/en-US/docs/Web/Manifest) and [service worker](https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API)
67
+
- App must pass [Store certification requirements](/windows/apps/publish/publish-your-app/msix/app-package-requirements)
68
+
69
+
**Limitations:**
70
+
- Deep native Windows APIs (file system access, hardware integration beyond Web APIs) are not available without additional bridging
71
+
- App logic runs in a web context — not suitable for apps that require native .NET, C++, or WinRT APIs
72
+
73
+
**When to choose this:**
74
+
- Your app is a web app, SaaS tool, or content site you want to make installable
75
+
- You want the fastest path to the Store with minimal tooling
76
+
- Your feature requirements are satisfied by modern Web APIs
77
+
78
+
→ [Overview of Progressive Web Apps](/microsoft-edge/progressive-web-apps-chromium/)
79
+
→ [Publish a PWA to the Microsoft Store with PWABuilder](https://docs.pwabuilder.com/#/builder/windows)
80
+
48
81
## MSIX sideloading — enterprise LOB distribution
49
82
50
83
For internal line-of-business apps that will be deployed to managed devices via Microsoft Intune or Configuration Manager, MSIX sideloading is the recommended path.
@@ -158,4 +191,5 @@ Regardless of your packaging format, you can submit a manifest to the [Windows P
158
191
-[SmartScreen reputation for Windows app developers](smartscreen-reputation.md)
159
192
-[Current status of Windows app distribution features](distribution-feature-status.md)
160
193
-[Publish to the Microsoft Store](/windows/apps/publish/)
194
+
-[Progressive Web Apps overview](/microsoft-edge/progressive-web-apps-chromium/)
0 commit comments