Then the Android Framework team decided to follow them. Instead Kotlin was intended to replace Java, the Android developers discovered and used it first. So it was not in fact like Swift which was invented and pushed by Apple for iOS developers. This explains neatly that while Kotlin is a big hit on Android, there are still as many or more Kotlin developers that are not programming for Android. On the other hand, while Android is a big platform, Java and the JVM is an even huger platform. The programmers interested in Swift and in iOS/macOS are basically the same.

Kotlin was created by JetBrains, not for Android but for Java and the JVM. Kotlin was designed for Java and the JVM, not for Android Some early articles even used this parallel explicitly: It seems that Google is pushing Kotlin in the exact same way. The background on this is that the Android world is becoming fast Kotlin first.Īlso there is a very tempting parallel with the Apple/iOS world where Swift is replacing Objective C. In the Android world, Kotlin is replacing Java But since the JVM is a bigger platform, the number of Kotlin developers that do Android or something else is roughly similar. They are doing a different job and a good recruiter is not required to know everything that we know, he needs to do his own job well.Īs you can see on this schema, Kotlin has a larger share of usage in Android than on the JVM. I have noticed that Android and Kotlin are increasingly becoming synonyms, especially in the minds of IT recruiters.

Internal in kotlin