Singletons vs. Application Context in Android?

by

I very much disagree with Dianne Hackborn’s response. We are bit by bit removing all singletons from our project in favor of lightweight, task scoped objects which can easiliy be re-created when you actually need them.

Singletons are a nightmare for testing and, if lazily initialized, will introduce “state indeterminism” with subtle side effects (which may suddenly surface when moving calls to getInstance() from one scope to another). Visibility has been mentioned as another problem, and since singletons imply “global” (= random) access to shared state, subtle bugs may arise when not properly synchronized in concurrent applications.

I consider it an anti-pattern, it’s a bad object-oriented style that essentially amounts to maintaining global state.

To come back to your question:

Although the app context can be considered a singleton itself, it is framework-managed and has a well defined life-cycle, scope, and access path. Hence I believe that if you do need to manage app-global state, it should go here, nowhere else. For anything else, rethink if you really need a singleton object, or if it would also be possible to rewrite your singleton class to instead instantiate small, short-lived objects that perform the task at hand.

More Related Contents:

  1. What is an efficient way to implement a singleton pattern in Java? [closed]
  2. Setting Singleton property value in Firebase Listener
  3. Why is volatile used in double checked locking
  4. Implementing Singleton with an Enum (in Java)
  5. MVC pattern on Android
  6. Double Checked Locking in Singleton
  7. Using Singleton design pattern for SQLiteDatabase
  8. What’s Alternative to Singleton
  9. Singleton Design Pattern: Pitfalls [closed]
  10. Why implementing a Singleton pattern in Java code is (sometimes) considered an anti-pattern in Java world?
  11. Other Ways of Singleton in Java [duplicate]
  12. How to change method behaviour through reflection?
  13. Android: Cannot perform this operation because the connection pool has been closed
  14. Parcelable and inheritance in Android
  15. should a db connection be a singleton?
  16. Get application context from non activity singleton class
  17. Java Singleton Pattern
  18. Why use a singleton instead of static methods?
  19. When would the garbage collector erase an instance of an object that uses Singleton pattern?
  20. Singleton pattern (Bill Pugh’s solution)
  21. How to create a singleton class
  22. Static references are cleared–does Android unload classes at runtime if unused?
  23. Sending arrays with Intent.putExtra
  24. Android Data Binding using include tag
  25. Fatal Error: Invalid Layout of java.lang.String at value
  26. Android Retrofit Design Patterns
  27. How to change fragments using Android navigation drawer
  28. AAPT: error: resource android:attr/fontVariationSettings not found and resource android:attr/ttcIndex not found
  29. android admob resize on landscape
  30. Using the camera activity in Android

Leave a Comment