- \n
- Operating systems manage the flow between operations.<\/li>\n\n\n\n
- This second type is called Cooperative multitasking, Operations control changes by itself.<\/li>\n<\/ol>\n\n\n\n
For that reason in the kotlin language, There is one concept called Coroutine<\/strong>. <\/p>\n\n\n\n
Coroutines were launched to Kotlin in version 1.3<\/strong>. Coroutine is basically a multitasking method. By use of this, we can perform multiple simultaneous processes. A coroutine is not a thread, a Coroutine is normally the same as a lightweight thread. <\/p>\n\n\n\n
In one thread, we can access the multiple coroutines. A coroutine can exchange the thread from one to another. But Sometimes, If the Programmer can\u2019t use the coroutine in the proper way then it\u2019ll create some issues. Like memory-related problems, Unnecessary problems will be created. <\/p>\n\n\n\n
![\"Android](\"https:\/\/www.oneclickitsolution.com\/blog\/wp-content\/uploads\/2021\/12\/Android-Custom-Library-CTA2.png\")
<\/a><\/figure>\n\n\n\nBefore starting the Demo of the Coroutine, you should have to clear some coroutine-related topics. Coroutine has some topic which is described below: Scopes, Dispatchers, and Suspend Functions.<\/strong><\/p>\n\n\n\n
1. Coroutine Scopes<\/h2>\n\n\n\n
The scope of Kotlin coroutines<\/a> can be defined as the constraints within which the coroutines are executed. Scopes help in modelling the lifecycle of coroutines. Kotlin coroutines have three basic scopes:<\/p>\n\n\n\n
- \n
- Global Scope<\/li>\n\n\n\n
- LifeCycle Scope<\/li>\n\n\n\n
- ViewModel Scope<\/li>\n<\/ul>\n\n\n\n
We can declare the dispatches in the Scope, at the end of all tasks we have to close that coroutine operation in scope. For this purpose, we can use the Scopes. If we destroy the \u201cScope\u201d then all the running tasks of that particular scope will also destroy with that Scope.<\/p>\n\n\n\n
2. Coroutine Dispatchers<\/h2>\n\n\n\n
Dispatchers are given the context of the coroutine code. So coroutine finds the thread where they are executed. Dispatchers have 4 types:<\/p>\n\n\n\n
- \n
- Main Dispatchers<\/li>\n\n\n\n
- IO Dispatchers<\/li>\n\n\n\n
- Default Dispatchers<\/li>\n\n\n\n
- Unconfined Dispatcher<\/li>\n<\/ul>\n\n\n\n
1. Main Dispatchers<\/h3>\n\n\n\n
Main dispatchers execute the coroutine on the main thread<\/strong>. The main dispatchers do most of the work on UI. It\u2019s also known as a UI thread<\/strong>.<\/p>\n\n\n\n
2. IO Dispatchers<\/h3>\n\n\n\n
IO Dispatchers initiate the coroutine on the IO thread<\/strong>, which helps to perform all data operations such as the internet, either reading or writing from the database, reading or writing to files, and so on. Data retrieval from a database is an IO operation performed on the IO thread.<\/p>\n\n\n\n
3. Default Dispatchers<\/h3>\n\n\n\n
Default dispatchers work on the default thread<\/strong>. When we want to do intricate and prolonged calculations that may cause the main thread to lag and the user display to become inaccessible, that\u2019s why we should use this dispatcher.<\/p>\n\n\n\n
4. Unconfined Dispatcher<\/h3>\n\n\n\n
Unconfined Dispatcher does not work on any particular thread. without requiring any particular threading strategy, permits the coroutine to restart in whatever thread is being utilized by the associated suspending function.<\/p>\n\n\n\n
3. Suspended Function<\/h2>\n\n\n\n
A function called suspend has three possible states: begun, stopped, and resumed. One of the most crucial things to keep in mind regarding the suspend functions is that they may only be invoked from another suspension function or a coroutine.<\/p>\n\n\n\n
Let\u2019s Start The Demo<\/h2>\n\n\n\n
We are creating one demo project to better understand the coroutine\u2019s work. In this project, we have 2 counters which increase from 1 to 10. the 1st counter will work at a 1-second delay. On the other hand, the 2nd one will work at a 3-second delay.<\/p>\n\n\n\n
At the bottom, there are 2 buttons, one for starting the process and the second one for stopping the counting. After the process there is one pop-up toast will be generated. So this is the work of our demo.<\/p>\n\n\n\n
First of all, you have to start with setting the dependency and Gradle settings. Which are shown below:<\/p>\n\n\n\n
\/\/build.gradle<\/p>\n\n\n\n
plugins {\n id 'com.android.application'\n id 'org.jetbrains.kotlin.android'\n}\nandroid {\n compileSdk 32\n defaultConfig {\n applicationId \"com.example.highlevelcoroutine\"\n minSdk 22\n targetSdk 32\n versionCode 1\n versionName \"1.0\"\n testInstrumentationRunner \"androidx.test.runner.AndroidJUnitRunner\"\n }\n buildTypes {\n release {\n minifyEnabled false\n proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'\n }\n }\n buildFeatures{\n dataBinding true\n }\n compileOptions {\n sourceCompatibility JavaVersion.VERSION_1_8\n targetCompatibility JavaVersion.VERSION_1_8\n }\n kotlinOptions {\n jvmTarget = '1.8'\n }\n}\n\ndependencies {\n implementation 'androidx.core:core-ktx:1.7.0'\n implementation 'androidx.appcompat:appcompat:1.5.1'\n implementation 'com.google.android.material:material:1.6.1'\n implementation 'androidx.constraintlayout:constraintlayout:2.1.4'\n testImplementation 'junit:junit:4.13.2'\n androidTestImplementation 'androidx.test.ext:junit:1.1.3'\n androidTestImplementation 'androidx.test.espresso:espresso-core:3.4.0'\n implementation 'androidx.lifecycle:lifecycle-viewmodel-ktx:2.4.0'\n}\n<\/code><\/pre>\n\n\n\nIf there is some dependency that will be deprecated then you can check from android\u2019s documentation.<\/p>\n\n\n\n
After the dependency work, We will start coding.<\/p>\n\n\n\n
First create the main activity and its layout. So we create on UI XML file and give the name like activity_main.xml, Its code is below:<\/p>\n\n\n\n
\/\/activity_main.xml<\/strong><\/p>\n\n\n\n
<?xml version=\"1.0\" encoding=\"utf-8\"?>\n<layout xmlns:android=\"http:\/\/schemas.android.com\/apk\/res\/android\"\n xmlns:tools=\"http:\/\/schemas.android.com\/tools\">\n\n <data>\n\n <\/data>\n\n <LinearLayout\n android:layout_width=\"match_parent\"\n android:layout_height=\"match_parent\"\n android:weightSum=\"3\"\n android:orientation=\"vertical\"\n tools:context=\".MainActivity\">\n\n <LinearLayout\n android:layout_width=\"match_parent\"\n android:layout_height=\"wrap_content\"\n android:layout_weight=\"1\"\n android:gravity=\"center\"\n android:orientation=\"horizontal\"\n android:background=\"@android:color\/holo_blue_dark\">\n\n <TextView\n android:layout_width=\"wrap_content\"\n android:layout_height=\"wrap_content\"\n android:layout_marginEnd=\"20dp\"\n android:text=\"@string\/the_counter_first_text\"\n android:textSize=\"32sp\"\n android:textColor=\"@color\/white\" \/>\n\n <TextView\n android:id=\"@+id\/the_first_counter_tv\"\n android:layout_width=\"wrap_content\"\n android:layout_height=\"wrap_content\"\n android:text=\"0\"\n android:textSize=\"30sp\"\n android:textColor=\"@android:color\/white\" \/>\n\n <\/LinearLayout>\n\n <LinearLayout\n android:layout_width=\"match_parent\"\n android:layout_height=\"wrap_content\"\n android:layout_weight=\"1\"\n android:gravity=\"center\"\n android:orientation=\"horizontal\"\n android:background=\"@android:color\/black\">\n\n <TextView\n android:layout_width=\"wrap_content\"\n android:layout_height=\"wrap_content\"\n android:layout_marginEnd=\"20dp\"\n android:text=\"@string\/the_counter_second_text\"\n android:textSize=\"32sp\"\n android:textColor=\"@color\/white\" \/>\n\n <TextView\n android:id=\"@+id\/the_second_counter_tv\"\n android:layout_width=\"wrap_content\"\n android:layout_height=\"wrap_content\"\n android:text=\"0\"\n android:textSize=\"30sp\"\n android:textColor=\"@android:color\/white\" \/>\n\n <\/LinearLayout>\n\n <LinearLayout\n android:layout_width=\"match_parent\"\n android:layout_height=\"wrap_content\"\n android:layout_weight=\"1\"\n android:gravity=\"center\"\n android:orientation=\"horizontal\"\n android:background=\"@android:color\/darker_gray\">\n\n <Button\n android:id=\"@+id\/btn_start\"\n android:layout_width=\"wrap_content\"\n android:layout_height=\"wrap_content\"\n android:layout_marginEnd=\"20dp\"\n android:backgroundTint=\"@android:color\/holo_green_dark\"\n android:text=\"@string\/start_text\"\n android:textAllCaps=\"false\" \/>\n\n <Button\n android:id=\"@+id\/btn_stop\"\n android:layout_width=\"wrap_content\"\n android:layout_height=\"wrap_content\"\n android:backgroundTint=\"@android:color\/holo_red_dark\"\n android:text=\"@string\/stop_text\"\n android:textAllCaps=\"false\" \/>\n\n\n <\/LinearLayout>\n\n <\/LinearLayout>\n<\/layout><\/code><\/pre>\n\n\n\nAfter completing the UI-related work we go to the MainActivity.kt File:<\/p>\n\n\n\n
\/\/MainActivity.kt<\/strong><\/p>\n\n\n\n
package com.example.highlevelcoroutine\n\nimport android.os.Bundle\nimport android.widget.Toast\nimport androidx.appcompat.app.AppCompatActivity\nimport androidx.lifecycle.Observer\nimport androidx.lifecycle.ViewModelProvider\nimport com.example.highlevelcoroutine.databinding.ActivityMainBinding\n\nclass MainActivity : AppCompatActivity() {\n \/\/for data binding\n private lateinit var activityMainBinding: ActivityMainBinding\n private lateinit var counterViewModel: CounterViewModel\n\n override fun onCreate(savedInstanceState: Bundle?) {\n super.onCreate(savedInstanceState)\n activityMainBinding = ActivityMainBinding.inflate(layoutInflater)\n setContentView(activityMainBinding.root)\n counterViewModel = ViewModelProvider(this)[CounterViewModel::class.java]\n counterViewModel.counter1Toast.observe(this@MainActivity, Observer {\n activityMainBinding.theFirstCounterTv.text = it.toString()\n })\n counterViewModel.counter2Toast.observe(this@MainActivity, Observer {\n activityMainBinding.theSecondCounterTv.text = it.toString()\n })\n counterViewModel.showToast.observe(this@MainActivity, Observer {\n Toast.makeText(this, it, Toast.LENGTH_SHORT).show()\n })\n activityMainBinding.btnStart.setOnClickListener {\n counterViewModel.startCounters()\n }\n activityMainBinding.btnStop.setOnClickListener {\n counterViewModel.stopCounters()\n }\n }\n}\n<\/code><\/pre>\n\n\n\nIn this, we will create one variable for our binding and another variable for our viewmodel.<\/p>\n\n\n\n
Before that, we will create our ViewModel and give its name like CounterViewModel.kt:<\/p>\n\n\n\n
package com.example.highlevelcoroutine\n\nimport androidx.lifecycle.LiveData\nimport androidx.lifecycle.MutableLiveData\nimport androidx.lifecycle.ViewModel\nimport androidx.lifecycle.viewModelScope\nimport kotlinx.coroutines.Job\nimport kotlinx.coroutines.delay\nimport kotlinx.coroutines.joinAll\nimport kotlinx.coroutines.launch\n\nclass CounterViewModel : ViewModel() {\n\n private fun showToast(message: String) {\n\n _showToast.value = message\n }\n\n private var counter1 = MutableLiveData(0)\n private var counter2 = MutableLiveData(0)\n private var _showToast = MutableLiveData(\"\")\n\n private var counter1Job: Job? = null\n private var counter2Job: Job? = null\n\n var counter1Toast: LiveData<Int> = counter1\n var counter2Toast: LiveData<Int> = counter2\n var showToast: LiveData<String> = _showToast\n\n fun startCounters() {\n counter1.value =0\n counter2.value =0\n counter1Job = viewModelScope.launch {\n for (i in 1..5) {\n counter1.value = (counter1.value ?: 0) + 1\n delay(1000)\n }\n }\n counter2Job = viewModelScope.launch {\n for (i in 1..5) {\n counter2.value = (counter2.value ?: 0) + 1\n delay(3000)\n }\n }\n counter1Job?.let { job1 ->\n counter2Job?.let { job2 ->\n val listOfJobs = listOf(job1, job2)\n viewModelScope.launch {\n listOfJobs.joinAll()\n showToast(\"Counters are completed.\")\n }\n }\n }\n }\n fun stopCounters() = viewModelScope.launch {\n counter1Job?.cancel()\n counter2Job?.cancel()\n }\n}<\/code><\/pre>\n\n\n\nHere, The main work of the application<\/a> will be done in this area. Creates two MutableLiveData initialized with the given value. And give it names like counter1<\/em> and counter2<\/em>. Make sure that these variables should be var and private. Create another variable for toast, this variable is the same as counter1<\/em> and counter2<\/em> but its value is not given like them, It\u2019s a string. <\/p>\n\n\n\n
And after this, for observing these variables in the main activity we are assigning these variables to the livedata variables. Make counter1Toast<\/em>, counter2Toast<\/em> and showToast and assign the above 3 MutableLiveData variables here. <\/p>\n\n\n\n
![\"Android](\"https:\/\/www.oneclickitsolution.com\/blog\/wp-content\/uploads\/2021\/10\/Android-vs-iOS-Mobile-App-CTA-1.png\")
<\/a><\/figure>\n\n\n\nAfter finishing the variable work, We will create one function called startCounter()<\/strong>. First set the value 0 to both counter variable 1&2. We have 2 types of counters, One will work on 1 sec delay period, and the Second one will work on 3 sec delay period. For this reason, we will create 2 variables of JOB. We will assign it as a null. counter1Job<\/em> will work on 1 sec delay period and counter2Job<\/em> will work on 3 sec delay period. We use the for loop to increment the counter to the 5 counts. With 1 and 3 sec delay. We will do this in Scope, viewmodelscope<\/strong> will use it for our processes. <\/p>\n\n\n\n
We will join both jobs cause toast should be shown if both jobs are done or canceled. For this, we use joinAll() function. JoinAll() is work to combine all jobs, If any job is not complete yet then it will not finish the process. So for that reason, we will scope function \u201clet\u201d<\/strong> and create one variable and assign the list of both jobs. And after this in viewmodelscope<\/strong>, we will join the list of both jobs. For showing the toast we will create one small function for toast. Give the name showToast() and put the parameter message and set it as a string. In this function assign the message to the _showToast MutableLiveData. It will show that toast when both jobs will complete. <\/p>\n\n\n\n
To stop the counting process, We will create one function called stopCounters()<\/strong>. In this, we will cancel both jobs. So automatically it will stop increasing the counting. For this reason, we will use the cancel() function. It will help to cancel both jobs.<\/p>\n\n\n\n
Here the main work is done. After completing this coding, we will go back to the Main activity to observe and set all live data variables to the text view and buttons.<\/p>\n\n\n\n
![\"First](\"https:\/\/www.oneclickitsolution.com\/blog\/wp-content\/uploads\/2022\/09\/First-event-when-completing-both-processes.gif\")
<\/figure>\n\n\n\n![\"Second](\"https:\/\/www.oneclickitsolution.com\/blog\/wp-content\/uploads\/2022\/09\/Second-event-Stop-processes-in-between-execution.gif\")
<\/figure>\n\n\n\n