It really depends on your use .
If your application data does not change much (think of a conference application that is used once or twice a year), you can use ContentProvider + CursorAdapters, which will simplify your life.
If your application data changes a lot (think of Gmail, where as many times as hundreds of emails can appear every day, or a news feed, or a social media application like Google+), then the database is likely to make your life worse. In this case, you must use a third-party caching system such as Google Volley or RoboSpice, etc., which handles all caching of JSON objects for you and all problems related to concurrency, etc.
Bogdan zurac
source share