Mobile game development / DIJION
Two devices, two saves: resolving mobile game progress conflicts
A save-selection guide comparing local, cloud and guest progress while explaining the limits of automatic merging.
A player can progress offline on a phone while opening an older save on a tablet. Both versions may contain distinct achievements when connectivity returns. Keeping the latest can be wrong when device clocks or game rules differ. In an illustrative level-based game, save selection is a product flow protecting effort, not merely a synchronization task.
Verify who owns the save
Guest progress, an app account and a platform account are not interchangeable identities. Establish ownership before replacing one save with another. Google Play Games cloud-save guidance explicitly addresses local/cloud conflicts and multiple accounts. It provides a relevant implementation reference, not a claim that every game must use that particular service.
Give the selection screen meaningful information
Scroll the table horizontally to see all columns.
| Information | What it explains | Limitation |
|---|---|---|
| Level position | Where the player reached | Does not describe every achievement |
| Play time | Recognizable context | Longer is not necessarily better |
| Save source | This device or cloud | Source does not establish superiority |
Merging needs explicit game rules
Adding two balances can count the same reward twice. Combining unlocked levels may be possible under different rules. Choose selection, merging or revalidation separately for each field. In a prototype, retaining a safe recovery copy while testing the decision helps reveal the consequences before committing to an irreversible replacement policy.
Explain replacement before confirmation
Name the save being selected instead of using an ambiguous Continue button. Explain whether the other version will be removed, what can be recovered and the scope of the change. An understandable choice may be preferable to silent automation under uncertainty. If connectivity fails during selection, wait for an actual accepted result before announcing success.
Conflict scenarios to exercise
- Progress offline to different levels on two devices.
- Link a guest session to an existing cloud account.
- Use different device clocks and inspect ordering decisions.
- Disconnect during selection and reconnect; protect the prior save.
Acceptance goes beyond choosing a winner: the player must understand the choice, progress must not cross into the wrong account, and retries must not duplicate it.