Chrome & PWA updates 2026: new features every web app builder should know

1. Richer install prompts — higher install conversion

The BeforeInstallPromptEvent (the browser API that triggers the "Add to Home Screen" prompt) got a visual overhaul. Chrome now shows a bottom sheet with the app's icon, name, description and screenshots — pulled directly from your manifest.json.

This matters because the old prompt was easy to dismiss without reading. The new one looks like a real app install dialog — comparable to the Google Play Store modal. Early data from Google shows conversion to install improved meaningfully with the new UI.

2. Web App Scope Extensions — your SaaS can span multiple origins

One of the most useful new APIs for SaaS products: Web App Scope Extensions. Until recently, a PWA's app scope was limited to its own origin. Navigate to a different subdomain or external URL and Chrome immediately opened the browser — breaking the "installed app" illusion.

With Scope Extensions, you can claim additional origins from your manifest:

// manifest.json
{
  "scope": "https://app.example.com/",
  "scope_extensions": [
    { "origin": "https://docs.example.com" },
    { "origin": "https://checkout.example.com" }
  ]
}

Navigation to those origins now stays inside the installed app. For a multi-product SaaS suite, this means a single app install covers your entire product surface.

Note: each extended origin must serve a valid /.well-known/web-app-origin-association file confirming the association. Same concept as assetlinks.json for TWA.

3. File Handling API — PWA as a real desktop app

The File Handling API is now available in Chrome on all platforms. It lets your installed PWA register as a handler for specific file types in the OS, just like native apps do.

// manifest.json
{
  "file_handlers": [
    {
      "action": "/open-file",
      "accept": {
        "text/csv": [".csv"],
        "application/json": [".json"]
      }
    }
  ]
}

Practical use cases: a SaaS data tool that opens .csv files on double-click, a project manager that handles .md files, an image editor that registers for .png and .jpg. The OS shows your app in the "Open with" menu — exactly like Figma, VS Code, or any native app.

For apps published to app stores via SaasToStore's desktop pipeline (Pake/Tauri), this behaviour can be configured natively in Tauri's tauri.conf.json — even deeper integration than the web API.

4. Protocol Handlers — deep links from other apps

Protocol Handler Registration lets your PWA register a custom URL scheme:

// manifest.json
{
  "protocol_handlers": [
    {
      "protocol": "web+yourapp",
      "url": "/handle?url=%s"
    }
  ]
}

Other apps or documents can then link to web+yourapp://action/id and the OS will route the user directly into your installed PWA — with the right context loaded. Think Slack'sslack:// links or Notion's notion:// deep links, but for any web app.

Combined with the deep linking feature in SaasToStore's PACK and PRO plans, this creates a seamless flow from external references directly into your SaaS product.

5. Push notifications on iOS — Safari finally compliant

Apple shipped Web Push support for installed PWAs in iOS 16.4 (March 2023), and continued improving it through 2024–2025. As of 2026:

• PWAs added to the home screen on iOS/iPadOS can receive Web Push notifications
• The W3C Push API and Notifications API are supported — the same code works across all platforms
• Limitation: the app must be installed (added to home screen) — Safari does not support push for in-browser PWAs
• Background sync and periodic background sync are still not supported on iOS (Chrome-only for now)

For products that span Android and iOS, this means one push notification codebase now reaches both platforms — provided users install the PWA on iOS. SaasToStore's push credits work with Firebase Cloud Messaging, which handles cross-platform delivery including iOS PWAs.

6. Improved offline capabilities — Storage Access API and OPFS

Two storage improvements ship in Chrome 2025–2026 and matter for offline-capable SaaS apps:

7. What TWA apps get automatically — no rebuild needed

This is the architectural advantage of TWA: apps published via a Trusted Web Activity use the device's installed Chrome as their runtime. When Chrome updates on the user's device, your Play Store app inherits all new PWA capabilities automatically.

How to check your PWA is ready for 2026

Run your URL through SaasToStore's free checker — it audits your manifest, service worker, HTTPS setup and Lighthouse score in one pass. If your PWA is ready for TWA packaging, you'll see a green score. If not, the checker explains exactly what to fix.