When to use a Content Provider

Question

I understand that Content Providers are made to allow publicly sharing data between applications. However, I\'m wondering if anyone has thoughts about making a Content Provi

Answer 1

As said in documentation: Creating a Content provider

You don't need a provider to use an SQLite database if the use is entirely within your own application.

So why bother developing this overhead? You want easier and faster development, right? So one layer of abstraction (SQLiteOpenHelper descendent) is enough.

See Occam's Razor Do not make an entities without very good reason.

Answer 2

I agree ContentProviders are a little difficult to grasp but they are definitely helpful, even if you want to use them internally for you own app. The best thing about it is that you can customize the contentproviders for suitable URIs.

Here's a scenario where you may have 5 tables in your database, but you need to join a few of them in certain orders before using them. And make a content URI for each of these joins. You could then each use these URIs as a table :)

I suggest you go ahead with Content Provider, you'll be amazed to see how powerful it is.

Answer 3

Do not use content provider if do not wish to share data with other apps. Use simple sqlitedatabase to perform database operations. Be careful while using content providers for storing confidential data because your confidential information may be accessed by other apps