Kotlin Became Google's Preferred Language for Android in 2019

There is a specific moment when a programming language stops being an alternative and becomes the default. For Kotlin and Android, that moment came on 7 May 2019, when Google announced at its developer conference that Kotlin had become the preferred language for Android app development. It was the clearest public signal yet that Google was committing the platform to Kotlin as the first-class path forward, rather than treating it as a Java companion.

The road to that announcement took years. Kotlin itself was developed by JetBrains, a company best known for building developer tools, and its first stable 1.0 release landed in February 2016. JetBrains had designed Kotlin not as a radical departure from Java but as a better language that stayed fully interoperable with it, allowing teams to migrate gradually. At Google I/O 2017, Google announced first-class support for Kotlin on Android, meaning the tooling, documentation, and platform guidance would treat Kotlin as an officially supported language rather than a community experiment.

The 2019 move up the scale, from supported to preferred, changed how the ecosystem behaved. New libraries started to ship idiomatic Kotlin APIs first, sample code increasingly appeared in Kotlin by default, and hiring teams began listing Kotlin as the expected language for Android roles. For working developers this was not a cosmetic label. Tooling defaults steer entire ecosystems, and once Google made Kotlin the preferred choice, Android Studio and the surrounding guidance naturally oriented around it.

From a senior developer's perspective, the Kotlin story is a textbook case of interoperability winning adoption. Kotlin runs on the JVM and interoperates fully with Java, which meant existing projects did not have to be rewritten to adopt it. Teams could introduce Kotlin file by file, side by side with Java, and let the compiler handle the boundary. That gradual migration path is why Kotlin spread as quickly as it did. A language that demands a big bang rewrite rarely succeeds; one that lets you start small and grow is far easier to justify to a cautious codebase.

The practical result is that Kotlin is now the language new Android developers are most likely to learn first, and the one the modern Android tooling assumes. Concurrency features like coroutines, null safety built into the type system, and concise expression-based syntax removed whole categories of bugs that Java developers had to watch for. It is not that Java cannot serve Android well, plenty of production apps still run on it, but the platform's center of gravity has shifted, and Google made that shift explicit in 2019.

The lesson for engineers is to watch what the platform vendor declares as preferred, because that is where tooling, libraries, and talent flow. Kotlin earned its position through genuine ergonomic wins, but it was Google's public endorsement that turned those technical advantages into the industry default. The right time to make that bet was not after everyone else did, but once first-class support landed in 2017 and you could already see the direction. Recognizing a preferred language early is a skill that pays off for the rest of a career.