Kotlin.
Kotlin is the official language for Android development: statically typed, null-safe, fully interoperable with Java, and the basis for Jetpack Compose and structured concurrency through coroutines. It also runs server-side and, through Kotlin Multiplatform, on other targets.
Where Kotlin fits on a long engagement.
Kotlin's null safety removes the single most common crash class in Android history, provided the boundary with Java is annotated properly. Platform types — values coming from unannotated Java whose nullability the compiler cannot know — are where that guarantee quietly lapses, and they are the thing to look for in a mixed codebase.
Coroutines are the other defining feature and the one most often misused. Structured concurrency makes cancellation and scoping explicit, but work launched in the wrong scope outlives the screen that started it, which shows up as leaks and as callbacks firing into a destroyed view. The discipline is about scope selection rather than syntax.
What an assigned team does with Kotlin.
Android estates tend to carry more historical Java than teams expect, so most Kotlin work is interop work. Judging which Java modules to annotate, which to convert and which to leave alone is a judgement about the specific codebase rather than a general rule.
That judgement improves with time on the same estate, which is the case for a dedicated development team rather than capacity assembled per release.
What we use Kotlin for.
- Converting an Android app incrementally Kotlin introduced file by file with interop annotations, so null safety is real rather than nominal.
- Concurrency that cancels correctly Coroutine scopes tied to lifecycle, so background work stops when the screen it belongs to goes away.
- Sharing logic across platforms Kotlin Multiplatform for business rules shared with iOS, where duplicating them has caused divergence.
How Kotlin capacity is assigned.
Kotlin capacity is assigned inside mobile development, and where the same team also owns backend services, across both rather than split into separate agreements.
Tell us what your roadmap needs Kotlin for.
A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.
Loading the contact form… You can also email hello@azendo.co.
We reply within one working day. No obligation, and no newsletter.