What is Jetpack Datastore? Why should we use Jetpack Datastore?
Post
Cancel

# What is Jetpack Datastore? Why should we use Jetpack Datastore?

## What is Jetpack Datastore? Why should we use Jetpack Datastore?

Hello everyone, In this article, I’ll talk about the DataStore structure, which is one of the Android Jetpack components. I’ll explain in code by giving examples with DataStore Preferences.

So what is a DataStore, why should we use it? Let’s start by giving information about!

## What is Datastore?

DataStore is a Jetpack component that is used to store our local data as an asecron with Kotlin Coroutine and Flow structures instead of SharedPreferences.

So why should we use this structure when there is SharedPreferences? Let’s explain by comparing the two structures.

### SharedPreferences vs DataStore

• DataStore and SharedPreferences both use the Async API. Datastore uses it for both writing and reading, while SharedPreferences only uses it to listen when changing variables.
• DataStore is safe to run under UI thread. Working with UI thread prevents ANR from occurring.
• DataStore is support error handling.
• DataStore is support kotlin kotlin-corutine and flow stuctures.

If we look at the this in more detail, there are two different type of structure. These;

• Preferences Datastore, this type stores data in key/value pairs like SharedPreferences but doesn’t provde any type of security.
• Proto Datastore this type stores data as objects,

We can provide storage using both types. But Proto provides type security. You also define a schema when using Proto.

You must define this schema under index src/main/proto/directory. This diagram contains the types of objects you’ll use.

More detailed information can be found at.

Let’s look at its setup and usage now.

….

### Datastore Preferences Setup and Usage

1 2 3 4 5 6 7 8 9 dependencies { // Preferences DataStore implementation "androidx.datastore:datastore-preferences:1.0.0-alpha02" // Proto DataStore implementation "androidx.datastore:datastore-core:1.0.0-alpha02" } 

We’ve added our Datastore libraries to project by including our dependencies in build.gradle.

Firstly we created class in the Datastore Preferences structure and created the data writing and reading fuctions that we’ll use.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 class BasePreferences(private val context: Context) { companion object{ val BASE_KEY = preferencesKey<String>(name = "key") } private val dataStore: DataStore<Preferences> = context.createDataStore( name = "pref" ) suspend fun saveValue(value: String){ dataStore.edit { preferences -> preferences[BASE_KEY] = value } } val lastSavedValue: Flow<String> = dataStore.data .map { preferences -> preferences[BASE_KEY] ?: "default value" } } 

Let’s simply show how we can write and use these values using to viewmodelScope in the viewModel.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 class BaseViewModel( private val app: Application, //repository ) : ViewModel{ var basePreferences = BasePreferences(app.applicationContext) var dataStoreLiveData: LiveData<String> = MutableLiveData() var baseValue :String = "" // we can write to value with the method. fun saveValue(val v : String){ viewModelScope.launch { basePreferences.saveValue(v) } } // The method we created to observe the data. // We can listen to our value in the activity or fragment class where we will use our view model. fun getLiveData(){ viewModelScope.launch{ dataStoreLiveData = basePreferences.lastSavedValue() .asLiveData(viewModelScope.coroutineContext+Dispatchers.Default) } } // we can read to value with the function. fun getValue(){ basePreferences.lastSavedValue() .collect { value -> baseValue = value } } } 

As I wrote in the commentline, we can listen to our livedata type variable in our activity or fragment class, where we’ll use our viewmodel and the necessary actions according to the charge.

Or we can collect and read data directly.

## Utilized Resources and Result

As seen in our examples, it is advantageous to use the DataStore Coroutine and Flow structure. It is a more reliable, more useful solution than SharedPreferences to securely perform asecron processing in UI threats.

See you in the next articles.