title: Dilemma: when to use Fragments vs Activities:
body: <p>I know that <code>Activities</code> are designed to represent a single screen of my application, while <code>Fragments</code> are designed to be reusable UI layouts with logic embedded inside of them.</p>
  <p>Until not long ago, I developed an application as it said that they should be developed.
  I created an <code>Activity</code> to represent a screen of my application and used Fragments for <code>ViewPager</code> or <code>Google Maps</code>. I rarely created a <code>ListFragment</code> or other UI that can be reused several times.</p>
  <p>Recently I stumbled on a project that contains only 2 <code>Activities</code> one is a <code>SettingsActivity</code> and other one is the <code>MainActivity</code>. The layout of the <code>MainActivity</code> is populated with many hidden full screen UI fragments and only one is shown. In the <code>Activity</code> logic there are many <code>FragmentTransitions</code> between the different screens of the application.</p>
  <p>What I like about this approach is that because the application uses an <code>ActionBar</code>, it stays intact and does not move with the screen switching animation, which is what happens with <code>Activity</code> switching. This give a more fluent feel to those screen transitions.</p>
  <p>So I guess what I'm asking is to share your current development manner regarding this topic, I know it might look like an opinion based question at first look but I look at it as an Android design and architecture question... Not really an opinion based one.</p>
  <p><strong>UPDATE (01.05.2014):</strong> Following this presentation by <strong>Eric Burke</strong> from <strong>Square</strong>, (which I have to say is a great presentation with a lot of useful tools for android developers. And I am not related in any way to Square)</p>
  <p><a href="http://www.infoq.com/presentations/Android-Design/" rel="noreferrer">http://www.infoq.com/presentations/Android-Design/</a></p>
  <p>From my personal experience over the past few months, I found that the best way to construct my applications is to create groups of fragments that come to represent a <strong>flow</strong> in the application and present all those fragments in one <code>Activity</code>. So basically you will have the same number of <code>Activities</code> in your application as the number of flows.
  That way the action bar stays intact on all the flow's screens, but is being recreated on changing a flow which makes a lot of sense. As Eric Burke states and as I have come to realize as well, the philosophy of using as few <code>Activities</code> as possible is not applicable for all situations because it creates a mess in what he calls the &quot;God&quot; activity.</p>