Skip to content

Commit f457eff

Browse files
novac42Lingyanmikehoffms
authored
Updated the guidance of packaging and publishing PWA (#3485)
* Updated the guidance of packaging and publishing PWA to call out that the feature is behind a feature flag and suggest developers to set initial availability to be false in the Json file. * writer pass * re-group sentences * described in * addressed the todos * re-seq notes about future * normalize manifest name --------- Co-authored-by: Lingyan <[email protected]> Co-authored-by: Michael S. Hoffman <[email protected]>
1 parent f459231 commit f457eff

File tree

1 file changed

+18
-8
lines changed

1 file changed

+18
-8
lines changed

microsoft-edge/progressive-web-apps/how-to/app-actions.md

Lines changed: 18 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
66
ms.topic: conceptual
77
ms.service: microsoft-edge
88
ms.subservice: pwa
9-
ms.date: 05/19/2025
9+
ms.date: 06/24/2025
1010
---
1111
# Enable App Actions on Windows for a PWA
1212

@@ -262,9 +262,7 @@ The above code is not in [Demos/wami/manifest.json](https://github.com/Microsoft
262262

263263
At the current stage, your PWA needs to be packaged as a Microsoft Store PWA, to be called by the Windows App Actions framework. You must use Microsoft Edge 137 or greater.
264264

265-
The Stable release of Edge 137 will be available on May 29, 2025. If you'd like to try it out before May 29, 2025, you can package your PWA in Edge Canary; see [Package a store PWA in Edge Canary](#package-a-store-pwa-in-edge-canary), below.
266-
267-
1. Upgrade to Edge Stable 137 version. (Edge 137 stable will be available after May 29, 2025.)
265+
1. Upgrade to Edge Stable 137 version.
268266

269267
1. Package your PWA for [PWABuilder.com](https://www.pwabuilder.com); see [Package your PWA for the Store](./microsoft-store.md#package-your-pwa-for-the-store) in _Publish a PWA to the Microsoft Store_.
270268

@@ -276,19 +274,31 @@ The Stable release of Edge 137 will be available on May 29, 2025. If you'd like
276274

277275
1. Click the **Download** button.
278276

279-
1. Unzip your download archive. Then you can [publish your PWA to the Microsoft Store](./microsoft-store.md) and install the app from the Store, or install it directly by running `install.ps1`.
277+
1. Unzip your download archive. Install it by running `install.ps1`.
280278

281279
1. Launch your PWA by clicking the PWA icon.
282280

281+
1. Test your PWA actions locally by following [Test App Actions for a PWA](#test-app-actions-for-a-pwa), below, to validate the functionality.
282+
283+
1. Open the action definition manifest file (such as `ActionsManifest.json`) that you used when packaging in PWAbuilder.com.
284+
285+
1. Set the initial availability of each of the app actions to `false`, as described in [Set initial availability](/windows/ai/app-actions/actions-availability#set-initial-availability) in _Toggle availability of an App Action for Windows_.
286+
287+
Before publishing your package, we recommend the above step. If you don't set the initial availability of the app action to `false`, your action will only work if the user manually goes to `edge://flags` in Microsoft Edge and then enables the feature flag `#edge-app-actions-on-windows-for-web-apps`.
288+
289+
Setting the initial availability to `false` is needed because Microsoft Edge's support of App Actions on Windows in PWAs is controlled by the feature flag `#edge-app-actions-on-windows-for-web-apps`, and is disabled by default, because this is a new feature in the Edge browser and is currently in Developer Trial<!-- not Origin Trial--> stage, as of June 26, 2025.
290+
291+
When the feature flag `#edge-app-actions-on-windows-for-web-apps` is officially rolled out (later in 2025),<!-- todo: update after rolled out --> Microsoft Edge will automatically switch the actions that you defined in the action definition manifest file from `Disabled` to `Enabled`, allowing end users to utilize your app's actions without requiring any further changes on your part.
292+
293+
1. Publish your PWA, as described in [Publish a PWA to the Microsoft Store](/microsoft-edge/progressive-web-apps-chromium/how-to/microsoft-store).
294+
283295

284296
<!-- ====================================================================== -->
285297
## Package a store PWA in Edge Canary
286298

287-
The Stable release of Edge 137 will be available on May 29, 2025; see [Package a store PWA in Edge Stable](#package-a-store-pwa-in-edge-stable), above.
288-
289299
Edge Canary gives a preview of the functionalities that's not available in stable yet.
290300

291-
If you want to try out App Actions for PWAs before May 29, 2025, you can package your PWA in Edge Canary, as follows:
301+
If you want to try out the latest capabilities of App Actions in Edge Canary, you can package your PWA in Edge Canary, as follows:
292302

293303
1. Install [Edge Canary](https://www.microsoft.com/edge/download/insider) and upgrade to the latest version.
294304

0 commit comments

Comments
 (0)