title: Is using Application context kind of God object antipatern
body: <p>I find that using application class to store some shared variables or to get to things like  PACKAGE_NAME or OS version via methods quite useful. This is because in this way you can get to this data from any component in your app and you can store objects that exist while your app is loaded, thus you avoiding some of GC and lifecycle problems. Although useful if used sparingly this seems like an antipattern to me. Because basically application class is doing too much. </p>
  
  <p>What I would like to know is what are your thoughts about this and should this approach be discouraged in favour of Persistent headless Fragment or some other approaches?</p>