Saving Data on Android

Ensures your UI matches your data state
: Since 
LiveData
 implements the 
observer pattern, you can be sure that your UI widgets such as 
Button
s, 
ListView
s, 
RecyclerView
s or 
TextView
s will always be updated with the 
latest 
information
.
•
No memory leaks
: Since 
LiveData
 observers are bound to the lifecycle of other 
components, they will be destroyed as soon as the associated component is 
destroyed.
•
No crashes due to stopped activities
: When an 
Activity
 becomes 
paused
 or 
stopped
 it won't receive any new 
LiveData
 notifications.
•
No more manual lifecycle handling
: Google made sure that 
LiveData
 
components are lifecycle-aware by default, so you don't have to manually control 
them.
•
Proper configuration changes
: Since 
LiveData
 is lifecycle-aware, and it caches 
the latest piece of data emitted, your Android components will receive the last 
emitted state, after configuration changes.
•
Sharing resources
: 
LiveData
 can be extended to wrap system services, so they 
can be shared in your app.
LiveData
 sounds awesome, right? Well, you are going to use it to wrap the results of 
your DAO queries, and as such, activities and fragments you use will automatically be 
notified of any changes. But, to do this, you need to add the 
LiveData
 dependency to 
your project, and change the DAO definitions, to return 
LiveData
s.