I\'m a bit confused in the question, if it\'s better to use ContentProvider or Database. Or it makes no difference if I don\'t want to share any da
Using a content provider will give you a more modular design, and make your life easier if you at some point in future would like to reach the data from other applications. If you are certain that the data will only ever be needed from one application, you might as well operate directly on the database.
There is one particular SQLite limitation you should be aware of and that is that SQLite is single-user only. What this really means is that you will need to guard your database from being accessed from multiple threads at the same time. This is generally not a problem in a content provider, since they almost always have a single-threaded implementation.