Signal

Nexora PWA

Service worker, install, and offline paths for learning — not a generic “Add to Home Screen” badge.

  • Installable PWA
  • Offline lesson paths
  • Lean runtime

Works alone

What it is

Built for a job, not a feature list.

Nexora PWA is two installable surfaces — the school and the chatbot — each with a service worker, manifest, and icons generated on the origin. Leitner and plan progress can live in an outbox and sync when the radio returns. It is not a generic “Add to Home Screen” badge.

Results

What changes on the site.

Two home-screen apps

Site and chatbot have distinct scopes, start URLs, and workers.

Offline schoolwork

Leitner CRDT and plan quiz outbox continue without a cell tower.

First-party offline page

A designed fallback, not the browser’s dinosaur.

Capabilities

What the package actually does.

  • Virtual manifest, service worker, offline page, health, install landing
  • Second scoped PWA for the chatbot
  • Install banner + beforeinstallprompt; generated icons 48–512
  • SW caches static assets and public plan JSON shells; skip-path list
  • Leitner offline CRDT client; plan progress/quiz outbox + sync REST
  • Cache-version bump on settings change; admin clear cache

Versus

Against the category leaders.

Honest deltas — not a fake scorecard. If a rival is better at a narrow job, the row says so.

Leader Where NexoraPlug differs
SuperPWA SuperPWA is a generic manifest. This ships dual apps and LMS-specific offline caches.
PWA for WP Same category. No Leitner CRDT, no chatbot-scoped second worker.
Progressier Progressier is hosted PWA SaaS. This generates workers on your origin with school caches.

Seat

The zip is not on the internet.

Packages live in a vault outside the web root. A key is HMAC-bound to your hostname. Verify and download are rate-limited. Updates stop when the seat is cold. We do not remote-wipe content you already have — PHP that WordPress requires to be GPL can be copied; stolen copies simply do not get the next build.

How a key behaves