Keep local state first and treat Persistly as the canonical sync target, not the only source of truth while offline.
Offline Sync Flow
Persistly works best when the game is local-first and sync-aware.
The right mental model is local gameplay state first, Persistly as canonical sync target second. That keeps offline play possible and makes sync pressure predictable.
Rules
Use these constraints as your baseline integration pattern.
Sync on meaningful lifecycle events such as foreground, background, checkpoint, prestige, or manual save moments.
Do not sync every frame or every tiny state mutation.
Lifecycle
Recommended sync cadence for idle and progression-heavy games.
Keep gameplay state locally while the game is running, even if the device is offline.
Persist saveId and the last canonical save snapshot after every accepted create, load, or sync response.
Sync on foreground, background, checkpoint, prestige, or manual save moments instead of on every state change.
If a conflict occurs, replace the canonical local snapshot with the server payload first, then decide whether to reapply local edits.