Skip to content
Tutorials Center
My learning

Topics

Lesson 5 of 37 ยท Getting Started

PWA Browser Support and DevTools

Know what PWA features work in Chrome, Edge, Safari and Firefox, and learn to debug manifests, service workers and caches with the DevTools Application panel.

PWA features are web standards, but browsers implement them at different speeds. Chrome and Edge lead, Safari has caught up in many areas but with its own rules on iOS, and Firefox focuses on the features that fit its desktop and Android strategy. Before you promise your users an installable, offline, notification-capable app, you need to know what each browser actually offers and how to debug the parts that break.

This lesson gives you a practical support map (details change, so always confirm on a compatibility site such as MDN's browser-compat data or caniuse) and a tour of the DevTools tools you will use every day.

Support at a glance

Feature Chrome / Edge Safari (iOS, macOS) Firefox
Service workers and Cache API Yes Yes Yes
Web app manifest Yes Yes (reads many fields) Partly (Android)
Install prompt (beforeinstallprompt) Yes No (manual Add to Home Screen) No
Installing a site as an app Desktop and Android iOS and macOS Dock Android; no desktop install
Web Push Yes Yes for installed web apps on iOS 16.4+ and in Safari on macOS Yes (desktop and Android)
Background Sync Yes No No
Periodic Background Sync Yes (installed apps) No No
App shortcuts, share target Yes Limited Limited

Take this table as a snapshot. The pattern to remember: service workers and caching work everywhere, the install and background features vary. Design so the core experience needs only the first row, and treat everything else as an enhancement.

iOS specifics you should know

  • Users install with Share, Add to Home Screen. There is no automatic prompt, so a custom install button cannot trigger it; you can only show instructions.
  • Push notifications on iOS only work for web apps that have been added to the Home Screen.
  • Storage is limited and may be cleared for sites the user has not visited for a long time (Safari's intelligent tracking rules), although installed web apps are treated more generously. Never treat browser storage as the only copy of important data.
  • Icons: iOS uses the apple-touch-icon link in many cases, so add one: <link rel="apple-touch-icon" href="/icons/icon-180.png">.

Detect, then enhance

You cannot rely on user-agent sniffing. Detect features directly. This stand-in prints a support report for the environment that runs it and shows how to build a reusable check.

JS Build a feature-support report

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The sandboxed preview here is an opaque origin, so some features report "no" even in a capable browser. That is a useful reminder: always test in the real page, on real devices.

The DevTools Application panel

In Chromium browsers press F12, open the Application tab (Edge calls it the same). Its left sidebar contains what you need.

Manifest

Shows the parsed manifest, the icons it found and any errors or warnings. It lists Installability problems in plain sentences, for example "No matching service worker detected" or "Manifest does not contain a suitable icon". You can also preview maskable icons and trigger the install flow from here.

Service workers

Lists registrations for the current origin with their status (installing, waiting, activated). Important checkboxes:

  • Offline simulates no network for this page.
  • Update on reload installs and activates a new worker on each reload, which saves you from stale caches while developing.
  • Bypass for network skips the service worker entirely, handy to compare with and without.
  • Buttons Update, Unregister, skipWaiting and the push, sync test fields let you fire events manually.

Storage

Cache storage shows every named cache and its entries; you can open entries, delete them and refresh. IndexedDB, Local storage and Session storage are listed too. At the top of the Storage overview there is a Clear site data button that wipes everything for a clean start.

The Network and Console panels

In Network, the Size column tells you the source: "(ServiceWorker)" means the service worker answered, "(disk cache)" the HTTP cache, a number means the network. The Offline throttling option in the same panel imitates a dead connection. In Console, set the context dropdown to your service worker file to see its console.log output; worker logs are separate from page logs.

flowchart LR
  A["Something is wrong"] --> B{"Which block?"}
  B --> C["Manifest panel: errors, icons"]
  B --> D["Service workers panel: status, update"]
  B --> E["Cache storage: what is stored?"]
  B --> F["Network: who answered?"]

Match the symptom to a panel.

Lighthouse

The Lighthouse tab audits your page. For PWAs, its Best Practices, Performance, Accessibility and SEO reports and the installability checks are most useful. Run it in an incognito window so extensions do not skew results. Chapter 7 shows how to read and improve the numbers.

Testing on real devices

An emulated phone in DevTools is useful for layout, but install behavior, push and storage need real hardware. Two techniques:

  • Remote debugging. Connect an Android phone by USB, open chrome://inspect, and inspect the phone's page with full DevTools. For iOS, use Safari's Develop menu with a Mac.
  • A tunnel or staging site. Real devices cannot reach your laptop's localhost over HTTPS. Use a tunneling tool or a staging deployment with a proper certificate, since service workers need a secure context.

A tiny debugging checklist

This stand-in turns the typical "why isn't it installable" investigation into a list of questions you can reuse. Edit the answers in the object and run it.

JS Stand-in: PWA debugging checklist

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The unchecked "workerControlsPage" item is a classic surprise: a service worker registered during the very first page load does not control that page until the next navigation, unless it calls clients.claim(). Chapter 3 explains this.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which feature works in all major browsers?

    Service workers and the Cache API have broad support; the others are Chromium-focused.
  2. 2. How do users install a web app on iOS?

    iOS has no install prompt event; users add the site manually from the Share sheet.
  3. 3. In the Network panel, what does '(ServiceWorker)' in the Size column mean?

    It shows that the response was produced by the service worker, for example from a cache.
  4. 4. Which DevTools option helps most against stale caches while developing?

    Update on reload installs and activates the newest worker at each reload.

Summary

  • Service workers and caches work in all modern browsers; install, push and background features vary, especially on iOS.
  • Detect features instead of sniffing user agents.
  • The DevTools Application panel covers Manifest, Service workers and Storage; Network shows who answered a request.
  • Test on real devices over HTTPS for install, push and storage behavior.

Next: Web App Manifest Basics