MAD Skills WorkManager : Wrap-Up
Posted by Caren Chang, Developer Relations Engineer
In case you missed it, we’ve just finished a MAD Skills series on WorkManager. We started by introducing WorkManager for those new to the library and then proceeded to talk more about advanced usages including how to test and debug your WorkManager code. The series ended with an episode on how to migrate your old code from GCMNetworkManager and FirebaseJobDispatcher to use WorkManager instead.
Here’s a quick summary of what we covered.
Episode 1: WorkManager: Basics
In our first episode, we explored the basics of WorkManager through the WorkManager codelab. We started by understanding how to define work we want done, and how to schedule the work. We then moved on to implementing different types of work: unique and periodic. Finally, we ended the episode by taking a look at app standby buckets to better understand how WorkManager schedules work.
If you’re new to WorkManager, we also recommend taking a look at the following articles:
Episode 2: WorkManager: Working in the background
The series continued with Ben giving a more in-depth look at how WorkManager deals with multi-threading. When working with threads, you have the option of using Executors, coroutines or RxJava, and Ben demonstrated each of these approaches with WorkManager. The episode concluded by demonstrating how to return a result when the work is completed so that the UI can be updated.
If you’re interested in using WorkManager with coroutines, we also recommend this article from Florina: WorkManager – Kotlin APIs
Episode 3: WorkManager: Advanced configuration and testing
In episode 3, we took a look at how to customize the initialization of WorkManager and support apps that span multiple processes. We’ve gotten a lot of questions from developers around testing and debugging, so Ben also dove into how to test your Workers, and useful debugging techniques.
Episode 4: Migrating from GCM NetworkManager and FirebaseJobDispatcher to WorkManager
In episode 4, we focused on how to migrate from old job scheduling libraries (GCMNetworkManager and FirebaseJobDispatcher) to WorkManager. Once your app starts targeting API level 30 and above, GCM NetworkManager and FirebaseJobDispatcher will no longer work on devices running Android Marshmallow (6.0) and above. If your app is still using either of those libraries, now is the time to update your apps to use WorkManager instead!
Episode 5: WorkManager with Hugo
Android GDE Hugo Visser talked about why he chose to use WorkManager in a health app he recently worked on and how the library has helped his development process.
Episode 6: Live Q&A
The series wrapped up with a live Q&A session where we answered your WorkManager related questions. Watch the recording to see all your questions answered, including future plans for WorkManager, handling duplicate work, retrying failed work, and more!
Related Google News:
- Bringing digital skills to previously incarcerated jobseekers April 29, 2021
- MAD Skills Motion Layout: wrap-up February 22, 2021
- Digital skills training for 100,000 Black women February 12, 2021
- Boost your query performance troubleshooting skills with Cloud SQL Insights January 28, 2021
- MAD Skills Kotlin and Jetpack: wrap-up January 15, 2021
- Digital tools and skills bring economic recovery in Canada December 15, 2020
- What’s your MAD score? December 15, 2020
- MAD Skills Material Design Components: Wrap-Up December 11, 2020