title: startActivityForResult vs accessing a static variable for the result
body: <p>I'm wondering if there's any downside to accessing a static variable in one Activity from another Activity instead of calling startActivityForResult() and waiting for the result to come back.</p>
  
  <p>In my example, I'm trying to retrieve a list of objects from a second activity. The first activity calls startActivityForResult. The second activity then allows a user to add different objects which CAN be stored statically in an ArrayList. But the way I'm doing it now is storing the objects in an SQLite table and then sending the column IDs back to the first Activity with Intent.putIntegerArrayListExtra(). The first array then searches for these IDs in the SQLite table and re-creates the objects.</p>
  
  <p>It would be way easier if I instead just accessed a static ArrayList of the checked items in the second activity. It works, but I am wondering if it is bad practice. If it's not bad practice, then the startActivityForResult() seems like a very convoluted way of exchanging data between two activities.</p>