Android Jetpack WorkManager Stable Release

Posted by Sumir Kataria, Software Engineering Lead and Jisha Abubaker, Product Manager

Streamline how you oversee foundation work with WorkManager

Today, we’re upbeat to declare the arrival of Android Jetpack WorkManager 1.0 Stable. We need to thank such a large number of you in our dev network who have given us input and logged bugs en route – we’ve arrived on account of your assistance!

When we took a gander at the top issues looked by designers, we saw that doing foundation preparing dependably and in a battery-accommodating way was an enormous test. This implied occasionally getting new substance or transferring your logs was intricate. Distinctive variants of Android gave diverse devices to the activity, each with their very own API eccentricities. For instance, tuning in for system or capacity accessibility and naturally retrying your errands included a great deal of work.

Our response to these difficulties was WorkManager. We presented a see of the Android Jetpack WorkManager library at Google I/O 2018 and have since iterated on it with extra highlights and bug fixes on account of your significant info.

The objective of WorkManager is to make foundation tasks simple for you. WorkManager considers imperatives like battery-enhancement, stockpiling, or system accessibility, and it possibly runs its errands when the proper conditions are met. It likewise realizes when to retry or reschedule your work- – regardless of whether your gadget or application restarts.

We trust WorkManager is a benevolent, receptive API that can deal with a standout amongst the most perplexing pieces of Android for you so you can concentrate on the code that makes your application one of a kind.

WorkManager Highlights

Here are some key highlights of WorkManager:

Gives you a chance to set limitations, for example, arrange status or charge state, on when the assignment runs

Supports nonconcurrent one-off and intermittent errands

Supports affixed undertakings with info and yield

Guarantees task execution, regardless of whether the application or gadget restarts

Supports Android 4.0+ (API 14+)

Watch and read beneath to realize when and how to utilize WorkManager to improve overseeing foundation work in your applications:

At the point when to utilize WorkManager

WorkManager is most appropriate for undertakings that can be conceded, yet are as yet expected to run regardless of whether the application or gadget restarts (for instance, matching up information occasionally with a backend administration and transferring logs or examination information).

For assignments like sending a text that are required to run promptly or for errands that are not required to pursue the application exits, investigate our experience handling manual for realize which arrangement addresses your issues.

The most effective method to utilize WorkManager

To begin with the WorkManager API, include the WorkManager reliance accessible Google’s Maven store in Java or Kotlin to your application’s build.gradle document:

conditions {

def work_version = 1.0.0


execution “$work_version”

/Kotlin KTX + coroutines

execution “$work_version”


Presently, basically subclass a Worker and actualize your experience work with doWork() and enqueue it with WorkManager.

class MyWorker(ctx: Context, params: WorkerParameters)

: Worker(ctx, params) {

supersede fun doWork(): Result {

/take every necessary step you need done out of sight here

return Result.success()



/alternatively, include limitations like power, organize accessibility

val imperatives: Constraints = Constraints.Builder()




val myWork = OneTimeWorkRequestBuilder()


WorkManager will presently deal with running your undertaking when it identifies that your gadget is charging and the system is accessible.

Why use WorkManager

In reverse similarity

WorkManager will use the correct planning API in the engine: it utilizes JobScheduler API on Android 6.0+ (API 23+) and a blend of AlarmManager and BroadcastReceiver on past renditions.

It likewise tries to guarantee the most ideal conduct so it follows framework advancements presented in fresher Android API forms to boost battery and uphold great application conduct.

For instance, WorkManager will plan foundation work amid the upkeep window for Android 6.0+ (API 23+) gadgets when the framework is in Doze mode.

Solid booking

With WorkManager, you can without much of a stretch include imperatives like system accessibility or charging status. Your work will run when the limitations are met and naturally retried on the off chance that they fall flat while running. For instance, if your assignment expects system to be accessible, the undertaking will be ceased when arrange is never again accessible and retried later.

You can likewise screen work status and recover work result utilizing LiveData. This enables your UI to be told when your errand is finished.

If your work comes up short, you can control how your work is retried by designing how backoff is taken care of.

WorkManager is additionally ready to reschedule your work, utilizing a record of your work in its nearby database, if an application or gadget restart happens.

Authority over how your work is run

We comprehend that each application has one of a kind needs, thus do your undertakings – even inside the equivalent application. WorkManager gives a basic yet profoundly adaptable API surface to help design your work and how it is run.

Exploit one-off booking with OneTimeWorkRequest or repetitive planning with PeriodicWorkRequest.

You can likewise chain your one time work solicitations to keep running all together or in parallel. On the off chance that any work in the chain falls flat, WorkManager tries to guarantee that the rest of the chain of work won’t run. Peruse progressively about tying work demands here.

On the off chance that you require greater adaptability over how WorkManager parallelizes and oversees work, look at our progressed stringing guide.

What designers need to state

redBus, the biggest online transport ticketing stage, shares their experience utilizing WorkManager to disentangle how they gather client criticism in their Android application:

“Input is basic to redBus as we venture into different nations. It regularly happens that a client gives basic criticism about a usefulness inside the redBus application however when the application endeavors to transfer the input to backend servers, there probably won’t be sufficient system inclusion or battery.

Leave a Reply

Your email address will not be published. Required fields are marked *