Firebase : What is the difference between setPersistenceEnabled and keepSynced?

Question

I thought the whole time when I used the following all data for chat conversation will be available offline at any time. Which somehow isn't and all nodes are loaded from the server.

FirebaseDatabase.getInstance().setPersistenceEnabled(true);

Then, according to DOCS :

Persistence Behavior : By enabling persistence, any data that we sync while online will be persisted to disk and available offline, even when we restart the app. This means our app will work as it would online using the local data stored in the cache.

If data will already be available offline when setPersistenceEnabled(true); , why do I need keepSynced(true) ?

DatabaseReference r = FirebaseDatabase.getInstance().getReference("chat/roomid");
r.keepSynced(true);

Answer 1

The Firebase Database client in your app can keep the data from the database in two places: in memory and/or on disk.

1. When you attach a listener, it synchronizes data from the database to an in memory representation in your app.
2. If you've enable persistence, the data is automatically also persisted on disk.
3. When you detach the last listener from a location, the data for that location is flushed from memory. But it is not deleted from disk.

When you keep a location synchronized, the client essentially attaches an empty listener to that location. So the data in the app will always be up to date with what's in the database on the server (as long as there is a network connection). If you haven't enabled persistence, the data will just be kept up to date in memory. If you've enabled persistence, it will also be kept up to date on disk.

While it's most common to use keepSynced with persistence, there are also use-cases without persistence.

For example, if you have a master-detail app, where you frequently bounce from a list of item names to the details of each item. In that case keeping the list of item names synchronized will save you from having to reload that data when the user comes back from the detail screen.

You could of course also simply keep a listener on the data, which is essentially what keepSynced does behind the scenes.