title: Multiple Activity or Single Activity and multiple fragments
body: <p>I have one very general question, I did not find a concrete answer for my question hence putting it again.</p>
  
  <p>I want to decide between two approaches</p>
  
  <ol>
  <li>Dedicated activities for various various screens and tasks to avoid complexity and issues</li>
  <li>Single Activities and multiple fragments for different tasks and user can navigate like Activity holding Fragment A user will navigate to Fragment B, Fragment C , this can be back and forth transaction.</li>
  </ol>
  
  <p>What I want to know?</p>
  
  <ol>
  <li>Is Activity transition is that costly for processor or to achieve simplicity memory overhead is negligible ?</li>
  <li>Fragment has overhead of managing life cycle with transition, so what all problem can come with this life cycler management?</li>
  <li>How easy is to deal with fragment transaction with saving state of the fragment?</li>
  </ol>
  
  <p>We don't know right now what amount data will be there for fragment to hold.</p>