title: Fragments seems to be overkill? No MVC architecture possible?
body: <p>i started with fragments a few days ago, but it seems wired for me. I dont see the justified advantage for the heavy increase of complexity.
  I dont know, if i should implement the functionality in my Activity or in my Fragment.
  First, i tried to put it in the fragments but that often seems to be not possible.</p>
  
  <p>For example:
  I have a dialog as user input, after button click.
  So i transfered the button click via listener from fragment to activity and in the activity i opened the dialog. In the dialog I started new functions (so implementation in Activity).
  Android dev gives the hint to add a alert dialog in a fragment:</p>
  
  <p><a href="http://developer.android.com/resources/samples/ApiDemos/src/com/example/android/apis/app/FragmentAlertDialog.html">http://developer.android.com/resources/samples/ApiDemos/src/com/example/android/apis/app/FragmentAlertDialog.html</a></p>
  
  <p>But this fragment still is implemented and heavy coupled with the activty (button action of the dialog is in the activity).</p>
  
  <p>So Model and View are heavy mixed up. I dont see a additional value in such an hard to maintain, static code?!</p>
  
  <p>Whats your opinion and advice about fragments?</p>