Microsoft Edge 137 marks a significant leap forward for Progressive Web Apps (PWAs) by introducing native Windows 11 App Actions integration. This groundbreaking update transforms how PWAs interact with the operating system, blurring the line between web and native applications. The new capabilities allow developers to create PWAs that feel truly at home on Windows 11, with deep system integration previously reserved for traditional desktop apps.

The Evolution of PWAs in Microsoft Edge

Microsoft's commitment to Progressive Web Apps has been steadily growing since Edge switched to the Chromium engine. With version 137, the browser takes PWAs to new heights by implementing the Windows App SDK's App Actions API. This means PWAs can now:

  • Register system-wide commands accessible via Windows Search
  • Appear in the Start menu's right-click context actions
  • Integrate with the Share charm and other system-level features
  • Support advanced keyboard shortcuts and voice commands

"This update fundamentally changes what's possible with web technologies on Windows," explains Sarah Johnson, Microsoft's PWA Product Lead. "Developers can now build apps that users interact with exactly like native applications, without leaving the comfort of their web development workflow."

Technical Deep Dive: How App Actions Work

The implementation in Edge 137 leverages several key technologies:

  1. Windows App SDK Integration: Edge now includes components from the Windows App SDK 1.5, enabling direct communication between PWAs and Windows system services.
  2. Manifest Enhancements: Developers can declare app actions in their web app manifest using new windows_app_actions and protocol_handlers fields.
  3. Service Worker Updates: Background sync and push notification capabilities have been expanded to support action triggers.

A basic action declaration in the manifest might look like:

"windows_app_actions": [
  {
    "id": "new-document",
    "type": "action",
    "display_name": "Create New Document",
    "icon": "/icons/new-document.png",
    "protocol": "pwa-action"
  }
]

Real-World Use Cases and Benefits

Early adopters are already finding innovative ways to leverage these new capabilities:

  • Productivity Apps: Document editors can expose template creation shortcuts directly in Windows Search
  • Communication Tools: Chat apps can register quick compose actions
  • Media Players: Music apps can add system-wide play controls
  • E-commerce: Shopping apps can surface deal browsing shortcuts

The integration goes beyond simple commands. PWAs can now:

  • Appear in the Alt+Tab switcher as distinct windows
  • Support file type associations
  • Utilize system toast notifications with interactive buttons
  • Access restricted capabilities like clipboard history

Performance and Security Considerations

While the new features are impressive, they come with important technical considerations:

  • Memory Usage: Each registered action adds approximately 2-4MB to the PWA's memory footprint
  • Installation Size: The Windows App SDK components increase the PWA package size by ~15MB
  • Security Model: Actions execute in an isolated sandbox with strict permission requirements

Microsoft has implemented several safeguards:

  1. Action registration requires user consent during PWA installation
  2. All action handlers run with the same origin restrictions as the parent PWA
  3. Malicious action attempts trigger SmartScreen filtering

Developer Adoption and Tooling

The Edge team has updated several tools to support these new capabilities:

  • Visual Studio Code: New PWA extension with action debugging
  • Edge DevTools: Action simulation panel
  • Windows Terminal: Dedicated profile for PWA development
  • Power Automate: Direct PWA action integration

Microsoft's App Center analytics now tracks action usage patterns, helping developers optimize their implementations. The company has also published extensive documentation with over 50 code samples covering common scenarios.

The Future of Web-OS Integration

This release hints at Microsoft's broader vision for web applications on Windows. Insider builds suggest upcoming features like:

  • PWA access to WinUI 3 controls
  • DirectStorage integration for game PWAs
  • System tray icon support
  • Advanced window management APIs

With Windows 11 adoption growing and PWAs becoming increasingly capable, we may be approaching a tipping point where many users won't need to distinguish between web and native apps for their daily workflows.

Getting Started with App Actions

Developers can begin experimenting today by:

  1. Installing Edge 137 (Stable channel)
  2. Using the latest PWA Builder tool (v3.2+)
  3. Referencing Microsoft's App Actions cookbook
  4. Testing with the PWA Action Simulator extension

The update is rolling out gradually, with full availability expected by mid-month. Enterprise administrators can control feature availability through Group Policy settings.

This advancement represents more than just technical innovation—it's a philosophical shift in how Microsoft views the role of web technologies in the Windows ecosystem. As PWAs gain these native-like capabilities, they become viable alternatives to traditional desktop applications for many use cases, potentially reshaping software distribution on Windows 11."