# Progressive Web App \(PWA\)

A progressive web app is a website enhanced with installable, resilient, and operating-system-integrated capabilities where browsers support them.

- Type: framework
- Domain: Engineering & architecture
- Level: Intermediate
- Last reviewed: 2026-09-23
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/progressive-web-app/>)

## What it means

A progressive web app \(PWA\) is a web application that uses standard web technology plus features such as a web app manifest and, when useful, a service worker. It can be installed and launched in an app-like window on supporting platforms while remaining addressable and usable as a website. PWA is a capability model, not a separate packaging format or a guarantee of offline operation.

## Why it matters

A PWA can broaden distribution without separate store binaries and can improve repeat access, resilience, and device integration. Its progressive nature lets a baseline web experience remain available when installation or advanced APIs are unsupported.

## When to use it

Consider PWA capabilities when repeat users benefit from installation, offline or poor-network support, notifications, or app-like launching. Verify platform support and product value before adding background behavior, caches, or prompts.

## How it works

1. Deliver a secure, responsive web application with stable URLs and a usable baseline.
2. Provide a web app manifest describing identity, icons, start URL, and display preferences.
3. Optionally register a service worker for controlled requests, offline behavior, and supported background features.
4. Meet browser-specific installability conditions and let users choose installation.
5. Test updates, storage eviction, offline failure, permissions, and uninstall behavior across target platforms.

## A practical example

A field-inspection service adds a manifest and caches the application shell, then stores draft inspections locally until connectivity returns. Inspectors can install it, but the same HTTPS URL remains fully usable in a browser.

## Where it breaks

Capabilities, installation surfaces, and background execution vary by browser and operating system. Offline data and updates create synchronization risks, permissions can be denied, and an installed window does not make a poor web experience native-quality.

## Common mistakes

- Defining a PWA as any site with a service worker.
- Assuming installation or offline support works identically on every platform.
- Showing disruptive install prompts before users understand the value.
- Caching responses without an update, expiry, and failure strategy.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/progressive-web-app/#visualization-progressive-web-app>)

## Sources

1. [What is a progressive web app?](<https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/What_is_a_progressive_web_app>) — MDN Web Docs · Official technical documentation
2. [Web Application Manifest](<https://www.w3.org/TR/appmanifest/>) — W3C · Web standard

## Related topics

- [Service Worker](<https://wiki.soroush.uk/topic/service-worker/>)
- [Web Storage](<https://wiki.soroush.uk/topic/web-storage/>)
- [Responsive Design](<https://wiki.soroush.uk/topic/responsive-design/>)
