An Android app could contain one or many activities. An activity has its own lifecycle and we can launch a new activity by using intents. In order to send data from an activity to another we could use a Bundle.
It’s time to continue our learning path in Kotlin. The subject covered in this new post is represented by Collections and data operations applied to them.
Collections are actually a set of classes and interfaces that provides high quality implementations of useful data structures and algorithms that help developers to reduce the programming effort and time.
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