Think of a Realm as a database.
A Realm is similar to a database and can contain different kinds of objects. You can use a Realm in your app instead of an SQL database.
The Realm is saved in a file on your device and can be backed up.
You can also create a Realm in memory which is destroyed when you close the realm.
Realm works seamlessly with Android and is very easy to set up and use.
Firebase is a Google product.
Use the start-up package for free and only start paying once you’ve expanded beyond the free package limits. You can check out the pricing here https://firebase.google.com/pricing/
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.
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?