The online save API provides user data storage for applications. It is useful for storing game states and other small data sets that a user may want to reuse later on a different device. There are API calls for submitting, retrieving, and removing data.
If you want to save frequently, such as when a player changes a setting, the code must buffer and retry failed submits. Submitting data could fail, if things are saved too freqently.
Minimize the amount of data that should be saved. Consider ways to compress data.
It’s better to have 1 bigger save rather than 5 smaller ones. Try to condense calls into a single one.
Avoid auto-saving using a timer. If you have no other choice, do it no more than once a minute.
Try to not exceed 30Kb. There is some headroom, but larger saves may get rejected by the API.