In this chapter, you will learn about content providers, one of the main building blocks of Android. In a nutshell, think of a content provider as an interface to your app’s data. Before we get to that, we need the data. So, we’ll talk about databases first.
In this chapter, you will learn how Android supports databases. You will learn to create and use a database inside the Yamba application to store your status updates locally. Local data will help Yamba display statuses to the user quickly, without having to wait for the network to provide the data. Our service will run in the background and periodically update the database so that the data is relatively fresh. This will improve the overall user experience of the application.
The Android system uses databases to store useful information that needs to be persisted even when the user kills the app or even shuts down the device and powers it back on. The data includes contacts, system settings, bookmarks, and so on.
So, why use a database in a mobile application? After all, isn’t it better to keep our data in a cloud where it’s always backed up instead of storing it in a mobile device that is easily lost or damaged?
A database in a mobile device is very useful as a supplement to the online world. Although in many cases it is much better to count on the data living in the cloud, it is useful to store it locally in order to access it more quickly and have it available even when the network ...