offline-queue

Buffer and replay API mutations for devices with intermittent connectivity.

Updated Mar 15, 2026

Search Tags:#mobile #swift #ios #persistence #sync #retry #offline-queue

Ready to run

npx skills add https://github.com/jtvaris/sunday-night-dynasty --skill offline-queue-jtvaris

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: offline-queue
Source: https://github.com/jtvaris/sunday-night-dynasty/tree/main/.agents/skills/generators/offline-queue
Command: npx skills add https://github.com/jtvaris/sunday-night-dynasty --skill offline-queue-jtvaris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Buffer and replay API mutations for devices with intermittent connectivity.

Core Features & Use Cases

Offline-queue with persistence and automatic retry
Conflict resolution and dependency handling for complex operation chains
Syncs pending mutations automatically when connectivity is restored

Quick Start

Instantiate the OfflineQueueManager with a persistence backend, start it at app launch, and enqueue operations when connectivity is offline.

Frequently Asked Questions about offline-queue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I queue API mutations in Swift when an iOS device loses connectivity?▼

You can queue API mutations in Swift by buffering them in an offline queue with a persistence layer, which automatically replays and syncs pending operations once network connectivity is restored.

How does an offline queue handle conflict resolution and operation dependencies?▼

An offline queue handles conflict resolution and operation dependencies by managing complex operation chains during synchronization, ensuring ordered execution and resolving data conflicts when replaying buffered mutations.

What is the best way to implement automatic retry for failed iOS network requests?▼

The best way to implement automatic retry for failed iOS network requests is using an offline queue with a configurable retry policy that buffers mutations, persists them, and automatically replays them when connectivity returns.

Can I use a custom persistence backend with an offline queue for iOS apps?▼

Yes, you can use a custom persistence backend with an offline queue for iOS apps, as the architecture requires a pluggable persistence layer to store queued mutations locally before automatic synchronization.

Do I need to manually trigger synchronization when the network reconnects?▼

No, you do not need to manually trigger synchronization when the network reconnects, because the offline queue automatically detects restored connectivity and syncs all pending mutations without user intervention.

How do I test enqueue and processing logic for an offline-first iOS app?▼

You can test enqueue and processing logic for an offline-first iOS app by using the queue's testable enqueue and processing API, which allows you to simulate intermittent connectivity and verify mutation replay behavior.