offline-first

To queue and replay mutations offline, you intercept mutation calls, store them in a local queue, and replay them automatically when connectivity is restored using a connectivity detection listener.

You can persist React Query cache offline by syncing query results to a Zustand store on success, then writing that state to MMKV for lightweight local persistence across app restarts.

The best way to handle optimistic updates with rollback is to apply the change to the local store immediately, and revert the state if the queued mutation fails during replay when online.

Yes, you can use an offline-first architecture with React Query and Zustand by syncing server data to a local store and toggling mutation queues based on network connectivity.

You detect network connectivity using native APIs or event listeners, and use the resulting online or offline status to toggle your mutation queue and trigger automatic replay.

Offline mutations fail to sync if the mutation queue lacks a connectivity listener to trigger replay, or if optimistic updates lack rollback logic to restore local state on replay errors.