Activities Lifecycle
<p>The Oreily Book Says:</p>

<blockquote>
  <p>Programming for Android is conceptually different than programming for
  some other environments. In Android, you find yourself more responding
  to certain changes in the state of your application rather than
  driving that change yourself.</p>
  
  <p>It is a managed, container-based environment similar to programming
  for Java applets or servlets.</p>
  
  <p>[...]</p>
  
  <p>So, when it comes to activity lifecycle, you don’t get to say what
  state the activity is in but you have plenty of opportunity to say
  what happens on transitions from state to state.</p>
</blockquote>

<p>Two Questions:</p>

<ol>
<li><p>What do they mean you find yourself more responding to certain changes in the state of your application rather than the driving the changes yourself" Please give an example.</p></li>
<li><p>Why don't you get to say what the activity is but get to say what happens on transition from state to state?</p></li>
</ol>
