title: Transfer values between two Activities with static fields
body: <p>Is there any disadvantage in transferring values from <code>Activity A</code> to <code>Activity B</code> with static fields of a third class instead of the <code>ExtraBundle</code>? </p>
  
  <p>In my application, sometimes I have like 15 - 20 values that I need to transfer between two <code>Activity</code>s. In my oppinion, it is more lucid solving this with static fields from a sort of <code>TransferHandler</code>. </p>
  
  <p>At the moment, I have one disadvantage in mind: When a value is not put into the <code>Extras</code> before starting <code>Activity</code> B, I will get an <code>Exception</code>. Solving it with static fields, it it possible that I forget to assign a value, and if that value was assigned before from somewhere else, it might be that a wrong value is used in <code>Activity</code> B. Nonetheless, I think this is a "programmer problem" and not a "program problem". So are there any further minusses or am I free to choice a way? How's with the performance of the two variants?</p>