Progressive Web Apps, or PWAs, have long treaded the line between the open flexibility of the web and the immersive, tightly integrated experience of native Windows applications. Now, with the release of Microsoft Edge version 137, Microsoft is making a significant play to make that boundary blurrier than ever: PWAs published to the Microsoft Store can now natively leverage Windows 11 App Actions.
App Actions in Windows 11 are essentially a new layer of interaction between installed applications and the operating system, enabling apps to declare contextual functions that users or the system can invoke at will. These are not just static shortcuts or links; App Actions can include automated business logic, dynamic responses, or direct integrations with Windows features or other apps.
At its core, this capability is reminiscent of the "contracts" mechanism from the Windows 8/RT era. Back then, contracts allowed Metro-style apps to expose searchable, shareable, and extendable capabilities to the system and each other. While some contracts, like Share, have quietly survived through to Windows 11, App Actions are a next-generation evolution designed for today’s far more modular and web-integrated environment.
Initially limited to a handful of Microsoft’s own in-box productivity apps under “Click to Do,” App Actions were hardwired into the OS. Only with the latest Patch Tuesday update—barely weeks old—has their public API been made widely available, expanding the vision from a closed loop to a new kind of developer platform. At the inaugural Build 2025 keynote, Microsoft formally opened App Actions as a platform capability, targeting those writing apps in C# or C++ with the Windows App SDK. And, crucially, starting now, PWAs wrapped via Microsoft Edge can enroll, too.
Practically, this means any PWA developer can declare contextual actions such as quick access points, text processing commands, or automation hooks. For example, a note-taking app could offer an “Add selection to notes” action from any text the user highlights in Windows, or a news reader might expose “Summarize article” triggered directly from the Start menu.
Goodnotes stands as the pioneer for this approach. The company’s PWA integrates as a selectable action for any marked-up text on screen. When a user highlights text anywhere in Windows and invokes App Actions, Goodnotes offers to capture and organize it—no cumbersome copy-pasting or context switching necessary. This is precisely the fast, inter-app workflow Windows 11 is attempting to foster across the ecosystem.
When a PWA developer publishes an app to the Store, they include a manifest describing available App Actions. Edge, upon detecting an eligible API call, registers those actions at the OS level. Once active, these commands are surfaced throughout Windows: context menus, right-click dialogs, or via agentic workflows initiated elsewhere in the system.
This system lends itself well to automation fans and power users, evoking the ethos of macOS Automation, Android Intents, or Apple’s Shortcuts. Windows 11, increasingly shaped by AI and agentic design patterns, is betting that cross-app, user-defined flows will become a norm for digital productivity in the coming years.
This could encourage cross-platform developers to double down on web technologies, building for Windows (and potentially other OSes) from a shared codebase without sacrificing integration or user engagement. Given that the Microsoft Store is now fully web-compatible, and Edge is a first-class citizen on both Windows and other platforms, this pathway lowers the friction and cost for app makers.
Enterprise users may soon leverage this for internal workflow automation, with in-house PWAs registering for bespoke business logic handled directly inside Windows.
For now, this comes via Edge 137, but successful adoption and positive developer feedback could encourage deeper integration with competing browsers—Chromium, Chrome, and even Firefox—should Microsoft choose to push for web standardization.
While Edge usage is growing due to its performance, security, and tight Windows integration, developers must be aware that features like App Actions won’t always work seamlessly in enterprise settings where alternative browsers or edge case deployment scenarios are standard.
Malicious web apps registered as PWAs could potentially try to exploit these hooks to phish for data, harvest sensitive text, or impersonate legitimate actions. Although Edge’s security architecture and Store vetting help mitigate some risks, end-users may not always be aware which app is managing what action. It is essential that Windows conveys clear, user-readable prompts and permission dialogs for potentially sensitive commands.
In terms of ecosystem, the move could help close the gap with ChromeOS and its close ties to the web; if Edge’s approach proves popular and Microsoft advocates for a broader web standard via the Chromium project, expect major browser vendors to start aligning or innovating in parallel.
The key questions to monitor in the coming months:
This transition is not without its hurdles. Reliance on Edge may irritate some, and current limitations mean this is the start—not the culmination—of PWAs as full citizens in the Windows universe. Security, trust, and coordination across browser vendors will require vigilance and advocacy. Still, it is rare to witness a foundational capability land with such immediate practical impact and such far-reaching promise for the future of cross-platform software.
If Microsoft’s gamble pays off, users, developers, and IT admins alike could enjoy a Windows where desktop workflows are richer, more contextual, and delightfully native-feeling—even when the code comes straight from the open web. This is nothing less than a reimagining of what apps can do—and which apps get to do it—on the world’s most popular desktop platform.
Source: Thurrott.com PWAs Now Support Windows 11 App Actions
What Are Windows 11 App Actions?
App Actions in Windows 11 are essentially a new layer of interaction between installed applications and the operating system, enabling apps to declare contextual functions that users or the system can invoke at will. These are not just static shortcuts or links; App Actions can include automated business logic, dynamic responses, or direct integrations with Windows features or other apps.At its core, this capability is reminiscent of the "contracts" mechanism from the Windows 8/RT era. Back then, contracts allowed Metro-style apps to expose searchable, shareable, and extendable capabilities to the system and each other. While some contracts, like Share, have quietly survived through to Windows 11, App Actions are a next-generation evolution designed for today’s far more modular and web-integrated environment.
Initially limited to a handful of Microsoft’s own in-box productivity apps under “Click to Do,” App Actions were hardwired into the OS. Only with the latest Patch Tuesday update—barely weeks old—has their public API been made widely available, expanding the vision from a closed loop to a new kind of developer platform. At the inaugural Build 2025 keynote, Microsoft formally opened App Actions as a platform capability, targeting those writing apps in C# or C++ with the Windows App SDK. And, crucially, starting now, PWAs wrapped via Microsoft Edge can enroll, too.
How PWAs Gain App Actions Support
With Edge 137, PWAs distributed via the Microsoft Store can register their capabilities using the App Actions API. This bridges what was previously a significant gap: web-based apps acquiring native-level integration with core OS features.Practically, this means any PWA developer can declare contextual actions such as quick access points, text processing commands, or automation hooks. For example, a note-taking app could offer an “Add selection to notes” action from any text the user highlights in Windows, or a news reader might expose “Summarize article” triggered directly from the Start menu.
Goodnotes stands as the pioneer for this approach. The company’s PWA integrates as a selectable action for any marked-up text on screen. When a user highlights text anywhere in Windows and invokes App Actions, Goodnotes offers to capture and organize it—no cumbersome copy-pasting or context switching necessary. This is precisely the fast, inter-app workflow Windows 11 is attempting to foster across the ecosystem.
The Technical Foundations
The App Actions API is exposed through the Windows App SDK. For classic native apps, it’s written in C# or C++. Microsoft has also ported these capabilities into the service shell of PWAs via Edge; the browser acts as the secure runtime environment, marshaling requests to the appropriate installed web app instance.When a PWA developer publishes an app to the Store, they include a manifest describing available App Actions. Edge, upon detecting an eligible API call, registers those actions at the OS level. Once active, these commands are surfaced throughout Windows: context menus, right-click dialogs, or via agentic workflows initiated elsewhere in the system.
This system lends itself well to automation fans and power users, evoking the ethos of macOS Automation, Android Intents, or Apple’s Shortcuts. Windows 11, increasingly shaped by AI and agentic design patterns, is betting that cross-app, user-defined flows will become a norm for digital productivity in the coming years.
Strengths and Opportunities
1. Genuine Native-Parity for PWAs
PWAs have always faced an uphill climb in competing with fully native UWP or Win32 apps when it comes to system-level integration. With App Actions, Microsoft brings them tantalizingly close—granting first-class capabilities for the most common workflows users expect from their favorite desktop tools.This could encourage cross-platform developers to double down on web technologies, building for Windows (and potentially other OSes) from a shared codebase without sacrificing integration or user engagement. Given that the Microsoft Store is now fully web-compatible, and Edge is a first-class citizen on both Windows and other platforms, this pathway lowers the friction and cost for app makers.
2. Better Productivity and Accessibility
The surface area for App Actions is broad. Any app that relies on turning selected text into a command—note-taking, translation, scheduling, research—can now participate in system-wide flows. This could dramatically cut down on repetitive copy-paste loops or clunky context-switching. It also serves accessibility; apps can expose functions tailored towards users with diverse input preferences or needs.Enterprise users may soon leverage this for internal workflow automation, with in-house PWAs registering for bespoke business logic handled directly inside Windows.
3. Evolution and Modernization
App Actions are a clear signpost of Microsoft’s broader strategy to modernize Windows without the fragmentation of the past. Rather than inventing yet another siloed platform, Microsoft is extending Windows’ existing, trusted APIs and deployment mechanisms (Store + Edge) to empower web apps, which now dominate new software development.For now, this comes via Edge 137, but successful adoption and positive developer feedback could encourage deeper integration with competing browsers—Chromium, Chrome, and even Firefox—should Microsoft choose to push for web standardization.
Critical Caveats and Early Risks
1. Platform Lock-In and Dependence on Edge
The most immediate limitation is that App Actions for PWAs rely strictly on the presence of Microsoft Edge version 137 or higher. PWAs running through alternative browsers or via pure web shortcuts will not gain this deep OS-level integration. This reinforces Microsoft’s ongoing strategy of making Edge the default infrastructure backbone for system features.While Edge usage is growing due to its performance, security, and tight Windows integration, developers must be aware that features like App Actions won’t always work seamlessly in enterprise settings where alternative browsers or edge case deployment scenarios are standard.
2. Narrow Initial API Surface
Though promising, the current implementation of App Actions is relatively limited. Beyond “text actions,” most of the capabilities demonstrated or documented are fairly basic. Extending this to more advanced automation, file handling, device APIs, or inter-app data exchanges will require subsequent updates to both the SDK and Edge’s internal plumbing. It is advisable for developers interested in sophisticated workflows to read the manifest documentation carefully and expect incremental rollouts.3. Security and Privacy Considerations
Any mechanism that allows apps—especially web apps—to interface deeply with the operating system inevitably raises both security and privacy questions. Microsoft has not yet fully disclosed the granularity or limitations of App Actions' access to user data.Malicious web apps registered as PWAs could potentially try to exploit these hooks to phish for data, harvest sensitive text, or impersonate legitimate actions. Although Edge’s security architecture and Store vetting help mitigate some risks, end-users may not always be aware which app is managing what action. It is essential that Windows conveys clear, user-readable prompts and permission dialogs for potentially sensitive commands.
4. Store-Only Availability
Another reason for measured optimism: current support is strictly tied to Microsoft Store-published PWAs. Side-loaded or developer-mode PWAs, common in testing or in enterprise IT environments, do not get App Actions integration—at least not in the public builds. This is presumably a concern around security and curation but it does artificially limit the reach and experimentation for grassroots or rapid prototyping.Comparison to Competing Platforms
The concept of system-wide quick actions is not unique to Windows. Apple’s Shortcuts in macOS allow deep automation ranging from simple file renaming to full-featured app scripting, while Android’s Intents ecosystem remains a gold standard for inter-app communication. What sets Windows’ approach apart is the focus on bringing these features to web-first apps using open standards, whereas other platforms still gatekeep most high-privilege API access to native binaries.In terms of ecosystem, the move could help close the gap with ChromeOS and its close ties to the web; if Edge’s approach proves popular and Microsoft advocates for a broader web standard via the Chromium project, expect major browser vendors to start aligning or innovating in parallel.
Developer View: Getting Started with App Actions
For developers, the pathway is now clear but requires attention to detail:- Step 1: Build and test your PWA, ensuring that its capabilities genuinely merit native-level actions.
- Step 2: Update to the latest Edge (137+) and ensure you’re running a compatible Windows 11 build.
- Step 3: Follow Microsoft’s documentation for preparing an App Actions manifest, declaring the hooks and commands your app should expose.
- Step 4: Package and publish your PWA to the Microsoft Store, submitting the necessary metadata for App Actions integration.
Future Outlook: What’s Next?
Microsoft has a clear incentive to make App Actions a tentpole feature—not only for Edge but for the Windows 11 platform at large. With agentic workflows gaining hype through AI assistants and proactive automation, Windows is staking its claim to a new breed of user experience: contextual, cross-app, and (crucially) web-first.The key questions to monitor in the coming months:
- Will Microsoft expand App Actions to cover more workflows (media controls, device sync, voice commands, deep AI integration)?
- Can they convince other browser vendors—especially Chrome and Firefox—to adopt or emulate the API, thus preventing fragmentation?
- Will advanced users and enterprise orgs see enough trust in Store-vetted PWAs to allow business-critical workflows?
- Can Microsoft guarantee security and privacy for these expanded privileges in an era of increasing web-based threats?
Conclusion: A New Chapter for Web and Windows Integration
For years, the open web and tightly integrated desktop ecosystems have been uneasy neighbors—close but rarely truly collaborative. With App Actions in Edge 137, Microsoft is making a bold bid to bring PWAs into the privileged fold, providing them with tools that previously only native apps could access.This transition is not without its hurdles. Reliance on Edge may irritate some, and current limitations mean this is the start—not the culmination—of PWAs as full citizens in the Windows universe. Security, trust, and coordination across browser vendors will require vigilance and advocacy. Still, it is rare to witness a foundational capability land with such immediate practical impact and such far-reaching promise for the future of cross-platform software.
If Microsoft’s gamble pays off, users, developers, and IT admins alike could enjoy a Windows where desktop workflows are richer, more contextual, and delightfully native-feeling—even when the code comes straight from the open web. This is nothing less than a reimagining of what apps can do—and which apps get to do it—on the world’s most popular desktop platform.
Source: Thurrott.com PWAs Now Support Windows 11 App Actions
