Offline-First Application Patterns

Quick Guide: Reads and writes go to a local database first and the network catches up afterwards. IndexedDB is the store — reached through a wrapper such as Dexie (reactive queries, larger) or idb (thin, ~1.2KB) — and every syncable record carries _syncStatus, _lastModified and _localVersion so the queue knows what is outstanding. Deletes are tombstones, never removals, or a delayed sync resurrects them. The Background Sync API is Chromium-only, so an online listener is the mechanism and background sync the optimisation.

Detailed Resources:

• examples/core.md — syncable entity, repository, sync queue with backoff, connectivity detection, optimistic updates, hooks for status and mutations
• examples/indexeddb.md — Dexie schema and migrations, the idb alternative, multi-tab coordination, quota management
• examples/sync.md — last-write-wins, field-level merge, conflict UI, version vectors, delta cursors, background sync, pull-push, status indicators
• reference.md — storage and conflict-strategy selection, troubleshooting by symptom, performance and security notes

Which path applies