I also see that by implementing a content provider on my SQLite database, I have obtained a guaranteed Android management singleton, but I use AndroidAnnotations, which can do singleton management for me , And from what I’ve read, it doesn’t seem like as long as I manage my open connections correctly, it is even recommended to use a single database helper.
Am I missing something? For a single database application, the Content Provider API looks very low-level and error-prone. Especially “manually” managing URI mapping and introducing a strange abstraction layer does not seem to add much value.
Then local SQLite DB Is your content provider valuable? If so, is there some framework that can generate my URI mapping for me, or does it strictly scroll by itself?
< p>Secondly, using the content provider can very easily take advantage of the Loaders framework (also found in the support library) and CursorLoader, which allows your UI to be automatically updated to data changes in the content provider. This can greatly reduce the overall activity The amount of template needed.
If the template of the Content Provider itself is a problem, then you can of course use a comment framework (such as ProviGen) to automatically generate most content providers for you.
There are also some features in Android that can only be done with the help of content providers, including custom search suggestions and sharing application private files to other applications (although extending ContentProvider’s helper FileProvider class is most of what you need) .
UI testing can be made easier, you can use the provided MockContentProvider to simulate a specific data set without changing your activity code (assuming it is of course just loading data from the Content Provider).
p>
I’m still new to Android development, but I can’t revolve around content providers, especially for a single application, single database SQLite data source to create one (if any) Benefits. I can see that if I want to use a sync adapter, I need a content provider, but honestly, the Sync API is so frustrating that I don’t think there is any advantage to using REST to scroll my own remote sync process.
I also saw that by implementing a content provider on my SQLite database, I got a guaranteed Android management singleton, but I use AndroidAnnotations, which can do it for me Example management, and from what I’ve read, it doesn’t seem like as long as I manage my open connections correctly, it is even recommended to use a single database helper.
Am I missing something? For a single database application, the Content Provider API looks very low-level and error-prone. Especially “manually” managing URI mapping and introducing a strange abstraction layer does not seem to add much value.
Then local SQLite DB Is your content provider valuable? If so, is there some framework that can generate my URI mapping for me, or does it strictly scroll by itself?
First of all, the Sync API is more than just loading data from the server. It controls the synchronization of updates and batches of other applications in the entire system, Make sure to connect before running and optimize the battery life of the entire system (as described in running Sync Adapters periodically and transferring data using sync adapters guide).
Secondly, using content providers can be very easy Utilizing the Loaders framework (which can also be found in the support library) and CursorLoader, it allows your UI to be automatically updated with data changes in the content provider. This can greatly reduce the amount of boilerplate required for the entire event.
If the boilerplate of the Content Provider itself is a problem, then you can of course use a comment framework (such as ProviGen) to automatically generate most content providers for you.
There are still some functions in Android that can only be provided in the content. It can be done with the help of the supplier, including custom search suggestions and sharing the application’s private files with other applications (although extending the ContentProvider’s helper FileProvider class is most of what you need).
UI testing can be changed To make it easier, you can use the provided MockContentProvider to simulate a specific data set without changing your activity code (assuming it is of course only loading data from the Content Provider).