Well, it's the next best thing since sliced bread! This is what they can do for you:
You use a content provider to make your database accessible to other apps.
You use a content resolver to access a database in another app.
We covered building our provider class in Part 1. Now in Part 2, we’ll see how we use the provider to access the database.
We will be accessing the database from within the app that created it but we will still use a content resolver to do so.
This is part 1 of creating our custom content provider. This is where we build our ContentProvider class.
In part 2, we'll show how we use the provider within the same app to access the database.
SQLite databases can only be used by the app that created it. However you can choose to share the database with other apps if you wish.
You will need a content provider to manage access to this shared database.
It takes care of data security and communicates between the database and any app wanting to use it.
So you’ve got this data that you need to save. Why not put it into a SQLite database?
Need to get user’s names, email addresses, telephone numbers?
In fact you can get the user to enter any text. Just define your fields in your layout. Then when the user touches the field, a keyboard pops up and they can enter the text.
Buttons are part of the app’s user interface.
They allow the user to interact with the app.
The user clicks the button and something happens.
The Action Bar is at the top of every activity screen
The app icon displays in it by default.
You can replace the app icon with your company logo if you wish.
You can also include tabs, drop-down lists, pop-ups and menus in the Action Bar.
I’ll show you how to include menu items as Action items in the Action Bar.