3
Feature Request: Add Offline Sync Layer to Supabase Client (Offline Cache + Auto Sync + Conflict Resolution)
Source: supabase/supabase#40664 · opened by @Nishal77
Overview Supabase currently lacks native support for offline first application behavior. Developers building mobile apps, PWAs, and applications operating in low connectivity environments must manually implement caching, queuing, and conflict resolution. An official Offline Sync Layer would greatly improve reliability and developer experience. Problem • No automatic caching of query results for offline reads. • Writes fail when the client is offline; no built-in write queue. • No delta based sync mechanism to fetch “changes since last update.” • Conflict resolution is entirely manual and inconsistent across apps. • Realtime subscriptions may miss events when reconnection occurs. These limitations make Supabase challenging for offline first mobile and field applications. Proposed Solution: Offline Sync Layer 1. Local Storage Adapter • Web: IndexedDB • Mobile: SQLite / MMKV • Node: file or memory adapter 3. Offl…
No pledges yet. Be the first to back this.
Comments
Similar requests
Cache layer on top of Postgres
5 votes · 0 comments
Native Google Sheets Integration with Supabase (Two-Way Sync)
1 vote · 0 comments
Feature Request: Support for config.toml.local (gitignored local configuration overrides)
4 votes · 0 comments
Individual NPM packages for supabase-js modules?
2 votes · 0 comments
Support skipping conflicting rows during CSV import
1 vote · 0 comments
No comments yet.