Android Jetpack: Easy background processing with WorkManager (Google I/O '18)
Why Stack Overflow recommends it
Stack Overflow users link it as the official introduction when answering questions about WorkManager, JobScheduler and background work, and to clarify what WorkManager is and is not meant for.
Recommended by 3 people across 3 different months, 2018 to 2018.
What it is
A Google I/O '18 session introducing WorkManager, the Android Architecture Components library for scheduling deferrable background work in a backwards compatible way. It covers job chaining, status tracking and how to run work safely in the background. Presented by Google's Android team (Sumir Kataria is listed in the metadata).
What people said
Recommends TapanHP · 2018-05 · Stack Overflow · on “What exactly is Android Jetpack?”
Basically it is just set of useful things combined and sorted under 4 categories Foundation Architecture Behavior UI Some of the core things like AppCompat library, Architecture components, Fragments, Animation and transitions and many more were added now in relative categories and these 5 things were newly added. Android Ktx [LINK] The purpose of Android KTX is to make Android development with Kotlin more concise, pleasant, and idiomatic by leveraging Kotlin language features such as extension functions/properties, lambdas, named parameters, and parameter default values Navigation [LINK] The Navigation Architecture Component simplifies the implementation of navigation in an Android app.This
Recommends MinceMan · 2018-06 · Stack Overflow · on “Scheduling Jobs with JobScheduler in Android”
One thing the Job Scheduler doesn't do well is ensure exact times for your job to run. I think this would be a case of working as intended. By playing with your params you might be able to fix it though. Technically now you should use WorkManager instead. There was a Google IO talk on it a couple weeks ago. [this video] [LINK]
Recommends Tobias · 2018-07 · Stack Overflow · on “How to avoid asynctask and WorkManager fetch same record of database”
You should try to accomplish one task by one mechanism only - otherwise you will always run into concurrency issues. What's buggy about `Workmanager? Maybe you have it set up incorrectly. There are good talks from the Google IO in Workmanager [this video] , If you really encounter a bug, file an issue. Furthermore there should be no need to use AsyncTask anymore, please try to avoid it completely as it really is very error prone . There are many better things for asynchrounous work (workmanager, coroutinen, rxjava, ...)
Cites ianhanniballake · 2018-05 · Stack Overflow · on “Android Jetpack WorkManager data retention policy”
As per the Work Manager I/O Talk [this video] , WorkManager is not meant to be your data store. You should continue to store your data in your own database.
Cites Nikolay Kulachenko · 2018-06 · Stack Overflow · on “Android WorkManager vs JobScheduler”
"WorkManager has a lot of nice features but its main goal is to use the JobScheduler's API on older devices"... Wait, but we already have some backports. What's wrong with them? To cut it short: FireaseJobDispatcher [LINK] is fine but it requires Google Play to schedule jobs which isn't good if we're targeting China, for example. Evernote's AndroidJob [LINK] is an excellent backport with a lot of functionality. Imho, it was the best choice for scheduling any work. But now the latest version of the library uses the aforementioned WorkManager under the hood. And, unfortunately, sooner or later the library will be deprecated [LINK] : If you start a new project, you should be using WorkManager i