title: ContentProvider or Singleton approach to Android database?
body: <p>I see people advocating both of these approaches when dealing with Android SQLite database. I personally prefer Singleton database locking pattern, but new development practices suggest to drop out Singleton pattern. </p>
  
  <p>And now I am confused whether to continue as I am used to or to start using something "new &amp; better". </p>
  
  <p>Which approach it future-proof? Is Singleton approach so bad that it will be abandoned in the future?</p>