title: Keeping data view/layout in Android after screen rotate/activity destroyed
body: <p>I'm a little confused about the <code>Activity</code> being destroyed and recreated when the user's device is rotated. </p>
  
  <p>I've been reading around, and I understand the rationale for doing so (it basically 'forces' the developer to make sure they haven't 'missed' anything upon rotation/language/other changes)</p>
  
  <p>I'm happy to respect best practice if it is seen as such, however it begs the question: </p>
  
  <p><strong>How do I 'remember' the state of the game/app, so that when the screen is rotated I have something from which to re-generate what the user was looking at?</strong> </p>
  
  <p>From what I can see, absolutely everything is destroyed, the base class constructor runs and all variables in the <code>Activity</code> are 'null'. </p>
  
  <p>I suspect the 'savedInstanceState' (<code>Bundle</code> class) is where I would collect that data, <strong>but reading around it only seems to be used for when the app is closed from lack of resources</strong> (and a few other extremely fringe cases)</p>
  
  <p>Am I misinformed or misunderstanding the purpose of savedInstanceState? Is it wise to abandon best practice (letting the <code>Activity</code> be destroyed) if I'm mindful enough to not miss anything upon rotation? Thanks in advance for any advice. </p>
  
  <p><em>I should note this question applies to game programming (I'm not using a layout XML)</em></p>