title: Is excessive threading a bad idea in Android?
body: <p>I have a fragment that fetches some data from a database, using a <a href="http://developer.android.com/reference/android/content/AsyncTaskLoader.html" rel="nofollow"><code>AsyncTaskLoader</code></a>, which the fragment will then display. The fragments are presented in a <a href="http://developer.android.com/reference/android/widget/ViewAnimator.html" rel="nofollow"><code>ViewAnimator</code></a>, and the user can add new instances of this fragment to the front of the ViewAnimator (However it can house 2 fragments at most, if the user requests a new fragment and size > 2 then the oldest fragment is removed using the <a href="http://developer.android.com/reference/android/app/FragmentTransaction.html" rel="nofollow"><code>FragmentTransaction</code></a> instance). </p>
  
  <p>I imagine a "worst-case" scenario where the user will flip through perhaps 30 fragments in a relatively short time-span, thus creating 30 separate threads. Is Android capable of managing all these threads(killing them etc.) by itself, or do I need to revise my code?</p>
  
  <p>The reason each fragment uses its own thread, instead of the activity just using one for all of them, is for the sake of modulartiy. I imagined it would be best if the fragment was self-contained.</p>