Feature: offline PWA with a service worker
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 10
- Forks
- 0
- Avg merge
- 2h 52m
- Merged PRs (30d)
- 20
Description
Tier 4 — feature idea
Why
The manifest and icons ship, so the app is installable — but there is no service worker, which the README and CHANGELOG both call out ("home-screen icons only; no offline mode"). An installed app that shows a connection error on the train is worse than no install prompt at all.
Evidence
LearnStack/wwwroot/manifest.json— no service worker registeredCHANGELOG.md[1.3.0] — "manifest and icons only; no offline/service worker"
Sketch
- Cache the app shell and static assets.
- An offline fallback page explaining that Blazor Server needs a connection.
- Queue "save this URL" actions taken offline and replay them on reconnect (pairs with the share target).
Notes
Blazor Server fundamentally needs a live circuit, so full offline use is out of scope — the goal is a graceful offline experience plus a save queue.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading LearnStack/wwwroot/manifest.json, the README, and the 1.3.0 entry in CHANGELOG.md to understand the current installable app and documented limitations. Define the app-shell cache, offline fallback, and save-queue behavior, with completion requiring graceful offline messaging and replay of queued “save this URL” actions after reconnecting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100