title: How many Activities vs Fragments?
body: <h2>Intro:</h2>
  
  <p>The basic "Fragments Tutorial" pattern goes something like this:</p>
  
  <ol>
  <li>On a tablet, have a list on the left, details on the right. </li>
  <li>Both are    <code>Fragments</code> and both reside in the same <code>Activity</code>. </li>
  <li>On a phone, have a
  list <code>Fragment</code> in one <code>Activity</code>. </li>
  <li>Launch a new <code>Activity</code> with the details <code>Fragment</code>.</li>
  </ol>
  
  <p>(e.g. <a href="http://android-developers.blogspot.com/2011/02/android-30-fragments-api.html" rel="noreferrer">Android 3.0 Fragments API by Dianne Hackborn</a> and the <a href="http://developer.android.com/guide/components/fragments.html" rel="noreferrer">Fragments API Guide</a>)</p>
  
  <p>On both devices, functionality is in the <code>Fragments</code>. (simple)</p>
  
  <p>On the <strong>Tablet</strong>, the whole app is <strong>1 <code>Activity</code></strong>, on the <strong>phone</strong>, there are <strong>many <code>Activities</code></strong>.</p>
  
  <hr>
  
  <h2>Questions:</h2>
  
  <ul>
  <li><strong>Is there a reason to split the phone app into many <code>Activities</code>?</strong></li>
  </ul>
  
  <p>One <em>problem</em> with this method, is that you <em>duplicate a lot of the logic</em> in the main Tablet <code>Activity</code>, and in the separate Phone <code>Activities</code>.</p>
  
  <ul>
  <li><strong>Would it not be easier to retain the 1 Activity model in both cases,
  using the same logic of switching <code>Fragments</code> in and out (just using a different layout)?</strong></li>
  </ul>
  
  <p>This way most of the logic resides in the <code>Fragments</code> themselves, and there is only a single <code>Activity</code> - less duplication of code.</p>
  
  <p>Also what I have read about the <code>ActionBarSherlock</code> is that it seems to work best with <code>Fragments</code> instead of <code>Activities</code> (but I have not worked with it yet).</p>
  
  <p><strong>Are the tutorials oversimplified, or have I missed something major in this approach?</strong></p>
  
  <hr>
  
  <p>We have tried both approaches successfully in the office - but I am about to start a bigger project and want to make things as easy for myself as possible.</p>
  
  <p>Some links to related questions:</p>
  
  <ul>
  <li><a href="https://stackoverflow.com/questions/20306091/dilemma-when-to-use-fragments-vs-activities">Dilemma: when to use Fragments vs Activities:</a></li>
  <li><a href="https://stackoverflow.com/questions/7718242/patterns-when-to-use-activity-transition-vs-dynamic-fragments">Patterns when to use Activity Transition vs Dynamic Fragments</a></li>
  <li><a href="https://stackoverflow.com/questions/10478233/android-need-some-clarifications-of-fragments-vs-activities-and-views">Android - I need some clarifications of fragments vs activities and views</a></li>
  <li><a href="https://stackoverflow.com/questions/11794784/activities-or-fragments-in-android">Activities or fragments in Android?</a></li>
  <li><a href="https://stackoverflow.com/questions/11701208/multiple-fragments-and-activities-interaction-design">Multiple fragments and activities interaction design</a></li>
  <li><a href="https://stackoverflow.com/questions/5695408/so-what-are-the-exact-advantages-of-fragments-in-android-3-0">So what are the exact advantages of Fragments in Android 3.0?</a></li>
  </ul>
  
  <hr>
  
  <h2>Updates</h2>
  
  <p>Started bounty on question - still not convinced about why I need to duplicate my app logic in my tablet activity and in each phone activity.</p>
  
  <p>Also found an interesting article by the guys at Square, which is well worth reading:</p>
  
  <ul>
  <li><a href="http://corner.squareup.com/2014/10/advocating-against-android-fragments.html" rel="noreferrer">Advocating Against Android Fragments</a></li>
  </ul>