This year was about new opportunities, new job, new team, GDE life, Agile Squads, Android, WorkManager, Kotlin, mentoring, courses and speaking at conferences and events like: Android Makers Paris, Workshop at Politehnica University Bucharest, Android Course at Google Atelierul Digital, DevTalks Bucharest, Droidcon Cluj-Napoca, Codecamp Bucharest, Workshop at SISC ASE, DevFest Bucharest, DevFest Craiova, Kotlin Everywhere Cluj-Napoca. ✨ ✨ ✨
In my previous article we discovered details about how Kotlin was designed, what is the philosophy behind this new programming language and how its popularity has grown over the past years.
In this article we’re going to continue with some basic concepts from Kotlin Wonderland like the available types, control flow instructions, equality checks and null safety.
At this moment, in the world, there are more than 5000 programming languages available. Now, the first question asked by us, the developers, is why do we need another programming language like Kotlin?
“WorkManager is a library for managing deferrable and guaranteed background work.”
- Android memory model
- Android battery optimizations
- Current background processing solutions
- Where is WorkManager placed in the background work schema
- WorkManager components: Worker, WorkRequest and WorkManager
- Input/Output Data
Until now, in order to perform background work in Android, developers had to choose between multiple execution options. At Google I/O 2018, the Android team launched WorkManager as part of the Android Jetpack.
This library provides a simple and clean interface to specify deferrable, asynchronous tasks and when they should run. This blog post is the first in a new series on WorkManager. The series will include an overview about the Android memory model, existing background solutions, what’s happening behind the scenes and why and when we should use WorkManager.