title: Android: Can An Activity Class Serve As A Context And FragmentActivties As Controllers?
body: <p>I am making an Android app and working on setting up an appropriate design pattern to delegate responsibilities.</p>
  
  <p>Its become clear that Android functions differently than iOS, in that you can only have one Activity active at a time and you cannot retain references to activities, you can only communicate through bundle passing.</p>
  
  <p>With that in mind I am thinking of setting up an MVC kind of pattern as follows:</p>
  
  <p>MainActivity as an Activity class that serves as a context(or 'master controller')</p>
  
  <p>All other classes will be FragmentActivity classes which are 'controllers'.</p>
  
  <p>The MainActivity class will then just swap in and out fragments as necessary but will also be able to reference and pass data to those fragments.</p>
  
  <p>Is this safe design practice or have I missed how to properly setup MVC in Android?</p>