nasandre/dnd-character-generator

Fork 0

Feature: Add service worker for offline support #82

New issue

Closed

opened 2026-08-17 10:03:45 +00:00 by nasandre · 1 comment

nasandre commented

2026-08-17 10:03:45 +00:00

Owner

Feature Request

Status: LOW PRIORITY
Priority: Low
Component: Frontend UX

Description

Implement service worker for offline functionality and improved user experience.

Required Features

Offline Support
- Cache static assets (CSS, JS, images)
- Cache API responses for offline use
- Offline-first data sync when online
Background Sync
- Queue API calls when offline
- Sync when connection restored
- User notification when sync completes
Service Worker Lifecycle
- Automatic update checks
- Cache invalidation strategies
- Push notifications for updates
Error Handling
- Offline error messages
- Retry logic for failed requests
- Clear sync status indicators

Implementation Options

Use Workbox (recommended)
Manual service worker implementation
PWA framework integration

Benefits

Better user experience
Reduced load times
Works in low-connectivity situations
Improved mobile experience

## Feature Request **Status:** LOW PRIORITY **Priority:** Low **Component:** Frontend UX ### Description Implement service worker for offline functionality and improved user experience. ### Required Features 1. **Offline Support** - Cache static assets (CSS, JS, images) - Cache API responses for offline use - Offline-first data sync when online 2. **Background Sync** - Queue API calls when offline - Sync when connection restored - User notification when sync completes 3. **Service Worker Lifecycle** - Automatic update checks - Cache invalidation strategies - Push notifications for updates 4. **Error Handling** - Offline error messages - Retry logic for failed requests - Clear sync status indicators ### Implementation Options - Use Workbox (recommended) - Manual service worker implementation - PWA framework integration ### Benefits - Better user experience - Reduced load times - Works in low-connectivity situations - Improved mobile experience

nasandre referenced this issue from a commit

2026-08-23 08:02:30 +00:00

Fix issues #81-#88: performance monitoring, admin dashboard, service worker, bundle size

openclaw commented

2026-08-23 18:41:37 +00:00

Owner

Automated triage (openclaw monitor):

Diagnosis

No service worker or PWA implementation exists in the Vite/React frontend
Frontend is a SPA with API calls to /api/* endpoints; no offline caching strategy
Static assets served via nginx in production; no cache-first strategy for assets or API responses
Background sync and offline error handling not implemented

Possible fix

Add PWA support via vite-plugin-pwa in frontend/vite.config.ts
Configure caching in vite.config.ts:
- Static assets (CSS, JS, images) with long-term cache
- API responses with cache-first strategy using IndexedDB
Implement background sync using Workbox's workbox-background-sync to queue failed requests when offline
Add service worker registration in frontend/src/main.tsx or root component
Create offline UI with error messages and sync status indicators
Set up cache invalidation strategies for app updates

Key files to modify:

frontend/vite.config.ts (add PWA plugin and caching config)
frontend/src/main.tsx (register service worker)
frontend/src/App.tsx (offline detection UI)
frontend/public/manifest.json (PWA manifest)

Notes / Questions

Should character/party data be cached for offline use, or just static assets?
What sync conflict resolution strategy is preferred (last-write-wins, manual merge)?
Should we implement a "read-only offline mode" or allow data creation while offline?
Do you need push notification support for updates?
Should the service worker be manually implemented or use Workbox?

Automated triage (openclaw monitor):  ## Diagnosis - No service worker or PWA implementation exists in the Vite/React frontend - Frontend is a SPA with API calls to `/api/*` endpoints; no offline caching strategy - Static assets served via nginx in production; no cache-first strategy for assets or API responses - Background sync and offline error handling not implemented ## Possible fix 1. **Add PWA support** via `vite-plugin-pwa` in `frontend/vite.config.ts` 2. **Configure caching** in `vite.config.ts`: - Static assets (CSS, JS, images) with long-term cache - API responses with cache-first strategy using IndexedDB 3. **Implement background sync** using Workbox's `workbox-background-sync` to queue failed requests when offline 4. **Add service worker registration** in `frontend/src/main.tsx` or root component 5. **Create offline UI** with error messages and sync status indicators 6. **Set up cache invalidation** strategies for app updates Key files to modify: - `frontend/vite.config.ts` (add PWA plugin and caching config) - `frontend/src/main.tsx` (register service worker) - `frontend/src/App.tsx` (offline detection UI) - `frontend/public/manifest.json` (PWA manifest) ## Notes / Questions - Should character/party data be cached for offline use, or just static assets? - What sync conflict resolution strategy is preferred (last-write-wins, manual merge)? - Should we implement a "read-only offline mode" or allow data creation while offline? - Do you need push notification support for updates? - Should the service worker be manually implemented or use Workbox?

openclaw closed this issue

2026-08-23 19:38:29 +00:00

No labels

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

nasandre/dnd-character-generator#82

No description provided.

Rows
Columns