In Getting started with WorkManager, we mentioned that WorkManager performs background work asynchronously on your behalf. The basic implementation addresses the demands of most apps. For more advanced use cases, such as correctly handling work being stopped, you should learn about threading and concurrency in WorkManager.
There are four different types of work primitives provided by WorkManager:
Workeris the simplest implementation, and the one you have seen in previous sections. WorkManager automatically runs it on a background thread (that you can override). Read more about threading inWorkerinstances in Threading in Worker.CoroutineWorkeris the recommended implementation for Kotlin users.CoroutineWorkerinstances expose a suspending function for background work. By default, they run a defaultDispatcher, which you can customize. Read more about threading inCoroutineWorkerinstances in Threading in CoroutineWorker.RxWorkeris the recommended implementation for RxJava users. RxWorkers should be used if a lot of your existing asynchronous code is modelled in RxJava. As with all RxJava concepts, you are free to choose the threading strategy of your choice. Read more about threading inRxWorkerinstances in Threading in RxWorker.ListenableWorkeris the base class forWorker,CoroutineWorker, andRxWorker. It is intended for Java developers who have to interact with callback-based asynchronous APIs such asFusedLocationProviderClientand are not using RxJava. Read more about threading inListenableWorkerinstances in Threading in ListenableWorker.