🎓 All Courses | 📚 Blazor WASM Syllabus
Stickipedia University
📋 Study this course on TaskLoco

Blazor WASM can be configured as a Progressive Web App (PWA), enabling offline support, installability, and background sync — without App Store distribution.

Enabling PWA at Project Creation

dotnet new blazorwasm --pwa -o MyPwaApp

What Gets Added

  • wwwroot/manifest.json — app name, icons, start URL, display mode
  • wwwroot/service-worker.js — base service worker
  • wwwroot/service-worker.published.js — production service worker with pre-caching

How Offline Works

The production service worker pre-caches all app assets at install time. Subsequent visits load entirely from cache — no network required.

Updating

When you publish a new version, the service worker detects the change and prompts the user to refresh. Handle this in service-worker.published.js.

Testing PWA Features

  • Use Chrome DevTools → Application → Service Workers to inspect
  • The Install prompt appears automatically when PWA criteria are met
  • Test offline by toggling offline in DevTools → Network

YouTube • Top 10
Blazor WASM: Progressive Web App Support
Tap to Watch ›
📸
Google Images • Top 10
Blazor WASM: Progressive Web App Support
Tap to View ›

Reference:

Wikipedia: Progressive Web Application

image for linkhttps://en.wikipedia.org/wiki/Progressive_web_application

📚 Blazor WASM — Full Course Syllabus
📋 Study this course on TaskLoco

TaskLoco™ — The Sticky Note GOAT