title: Singletons vs. Application Context in Android?
body: <p>Recalling this <a href="http://www.antonioshome.net/blog/2006/20060906-1.php" rel="noreferrer">post enumerating several problems of using singletons</a>
  and having seen several examples of Android applications using singleton pattern, I wonder if it's a good idea to use Singletons instead of single instances shared through global application state (subclassing android.os.Application and obtaining it through context.getApplication()).</p>
  
  <p>What advantages/drawbacks would both mechanisms have?</p>
  
  <p>To be honest, I expect the same answer in this post <a href="https://stackoverflow.com/questions/2709071/singleton-pattern-with-web-application-not-a-good-idea">Singleton pattern with Web application, Not a good idea!</a> but applied to Android. Am I correct? What's different in DalvikVM otherwise?</p>
  
  <p>EDIT: I would like to have opinions on several aspects involved:</p>
  
  <ul>
  <li>Synchronization</li>
  <li>Reusability</li>
  <li>Testing</li>
  </ul>