Implement offline-first subscription data synchronization layer with CRDT

[Smartdevs17]

Context

The SubTrackr mobile app becomes unusable when the device loses network connectivity. Users managing critical subscription data need full read/write capability offline, with automatic conflict resolution when connectivity resumes. Currently, all subscription mutations require an active network connection.
\

\

Current Limitation

\

• All subscription CRUD operations require network access
  \
• No local-first data model; app state is ephemeral without network
  \
• Conflicts from concurrent offline edits have no resolution strategy
  \
• No sync status indicators for pending/conflicting changes
  \

\

Expected Outcome

A robust offline-first layer using Conflict-free Replicated Data Types (CRDT) enabling full subscription management offline, with automatic background synchronization and conflict resolution upon network recovery.
\

\

Acceptance Criteria

\

• Subscription CRUD operations work fully offline with local persistence
  \
• CRDT-based merge strategy resolves concurrent edits without data loss
  \
• Sync status indicator shows pending, syncing, conflict, and error states
  \
• Background sync triggers on network recovery with exponential backoff
  \
• Unit tests cover offline create/update/delete and conflict scenarios
  \
• Integration tests verify sync ordering and idempotency
  \
• Documentation updated for offline architecture and sync guarantees
  \

\

Technical Scope

\

• Files: src/services/cache/, src/store/subscriptionStore.ts, src/hooks/useOfflineSync.ts, src/services/network/networkMonitor.ts
  \
• APIs: Zustand store middleware for offline persistence, AsyncStorage/SQLite local DB, NetInfo for connectivity detection
  \
• Edge cases: Large offline mutation queues (>100), storage quota limits, partial network recovery, concurrent offline edits, subscription deletions during offline period

[AnnabelJoe]

@AnnabelJoe has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would like to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @AnnabelJoe to this issue.