Cloud Saves and Achievements Integration

Cloud Saves and Achievements Integration

Player beat 40 levels on iPhone, reinstalled on iPad—progress zeroed. Not "minor oversight". According several mobile studios, progress loss on reinstall is top-3 cause of negative reviews and game abandonment. iCloud or Google Play Games Services solve problem—but correct integration requires more than one method call.

Complexities Not Visible Until Production

Save merge conflicts. User played offline on two devices. When both connected—two incompatible progress snapshots. Apple Game Center and Google Play Games don't solve conflicts: they return both snapshots waiting client to choose winner. Without implemented conflict resolution with clear UI ("Your progress this device: 43 levels / In cloud: 38 levels—keep which?") user gets data loss.

Save size and write frequency. Google Play Saved Games limits snapshot 3 MB, total per account—10 MB (default). If save includes inventory with thousands records—need serialize only delta or optimize format. Frequent auto-saves (after each action) create queue accumulating poorly at bad connection, causing GooglePlayGames.SavedGame.ISavedGameClient timeout.

Apple iCloud Keychain vs CloudKit. For simple games NSUbiquitousKeyValueStore sufficient—syncs to 1 MB key-value pairs. For complex progress need CloudKit with CKContainer and CKRecord. Unity has no native CloudKit binding—integration requires Objective-C/Swift plugin or third-party like CloudSave from Unity Gaming Services.

Unity Gaming Services Cloud Save

For cross-platform (iOS + Android + PC) optimal—Unity Cloud Save from com.unity.services.cloudsave package. Stores JSON-documents up to 1 MB, works via Unity Authentication (anonymous accounts or federated identity), supports server-side validation via Cloud Code.

Key moment: CloudSaveService.Instance.Data.Player.SaveAsync()—async, throws CloudSaveValidationException on quota exceed and CloudSaveException on network errors. Production handling mandatory—without it connection loss during save breaks local cache without diagnosis.

Architecture: local save (PlayerPrefs or custom JSON in Application.persistentDataPath) + cloud as mirror with version tag. On load—compare cloud snapshot updatedAt metadata with local timestamp. If divergent—initiate conflict resolution flow.

Achievements

Google Play Games Achievements and Apple Game Center Achievements—different APIs, different limits, different unlock logic. Proper abstraction: IAchievementService with methods Unlock(achievementId), Increment(achievementId, steps), Report(achievementId, percent)—platform-specific implementation hidden behind interface.

Important detail: incremental achievements in Google Play require pre-setup totalSteps in Play Console. If steps changed (like "kill 100 enemies" became "kill 50")—can't change total steps without resetting entire player progress. This architectural decision made before release.

For Game Center on iOS—handle GKLocalPlayer.localPlayer.authenticateHandler with branching for: auth successful, user declined, Game Center unavailable. Last case often ignored—happens with Family Sharing restrictions.

Timeline

Cost calculated individually after auditing game architecture and sync progress requirements.