Thanks for the request! PWA support is a reasonable addition for a self-hosted tool that people are running behind reverse proxies and accessing from mobile.

What's needed for a minimal PWA:

/manifest.json (or manifest.webmanifest) — name, icons, display: standalone, start_url, theme color
A service worker (sw.js) — at minimum a simple fetch/cache handler; offline support can be as simple or complex as desired
<link rel="manifest" href="/manifest.json"> in <head>
App icons in multiple sizes (192×192, 512×512, SVG preferred)

Current state: The WebUI already has a favicon, so the icon asset work is partially done. The Flask server would need to serve manifest.json and sw.js as static files (trivial to add as a static route or just drop them in /static).

Scope notes:

An "installable" PWA (Add to Home Screen prompt) just needs the manifest + HTTPS + service worker. This is low-complexity.
Full offline support would require caching the API responses and session data — significantly more work and arguably not useful for a tool that requires a live backend connection anyway.
A minimal offline fallback page ("You're offline — the WebUI requires a server connection") is a good middle ground.

Adding to the backlog. A PR with a minimal manifest + service worker (installable, no offline caching) would be a straightforward first step.

PWA would be nice #685

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions