design patterns for persisting state on android app
<p>For android I am trying persist state if onDestroy() is called.  I'm wondering what are common design patterns used to do such a thing so that the actual app functionality is decoupled from the persistence functionality?  For example, I have a for loop that iterates through all of the players in the game.  This update happens at the end of each round in the game.  Would it be possible that the app gets destroyed half way through the update?  If that happened, what kind of logic would i need to include to remember which player was updated.</p>
