A couple of weeks ago, when going over some Android DevSummit videos, I encountered in some question about alternative language for Android during one of the fireside chats session with the Android team. It was really interesting that there was another way to develop an Android apps but unfortunately I didn’t fully catch the name of the language (“What what? was it Kotin? Tolkin? What he was saying???”) so I give up.
Next, I stumble upon this twitter conversation and finally found Kotlin:
What’s wrong with Java?
Nothing special, really. Yes, ruby python and JS are really sexy with all those duck typing and lambdas and much less boilerplate code, but Java has really good IDE’s that saves you a lot of time and don’t bother you with all those declarations.
Moreover, Oracle is trying to keeping up the pace and add some cool things like lambda expressions, but still- Java is a bit “heavy” and fall in the small things (like arrays and lists, NPE, iterations, Generics and more…).
So what’s wrong with Java on Android?
OK, that’s a different question. First- Java 8 (and even some things from Java 7) not supported on Android platform (yet, there was some changes in the last week and Google announce that the next version of Android will be targeting OpnJDK). So it still sucks to handle with stream, dates and we can’t use things like lambdas or switch on strings.
Second- Android considered as front end platform and as frond end developer I would like the code will be as lightweight as possible. That’s mean things like:
- Easily add helper methods to all kinds of types (and not using static utils classes everywhere).
- Lambda/ function pointers/ on the fly code execution.
- Easily run things in background and async task, without the callback hell.
- I would be glad to extends from my own classes by most of the time I must extends from Android classes (or other 3rd libraries) what make the code reuse and abstraction a bit hard.
Kotlin to the rescue
Statically typed programming language for the JVM, Android and the browser
JetBrains, the company behind Kotlin, understand the potential of Android build system and integrated the language compiled byte code straight into the Android gradle mechanism.
I won’t go over the language syntax, there is a very good documentation in the Kotlin site. I would just say that for Java devs among you it suppose to be pretty straight forward, and for you who familiar with C# it should be even easier.
Starting with android
So lets start by creating an Android project. JetBrains are also the creator of InteliJ, the editor Android Studio based on, so it easily integrated for working also with Kotlin, you just need to install the Kotlin plugin.
Creating a new Android app with Kotlin it just like a regular app, follow this instructions and make the first “Hello World” app. You might still gonna need to do some changes in code (like changing from savedInstanceState: Bundle to savedInstanceState: Bundle? for null safety) but it suppose to compile quickly.
Now we’re able to see how we can use the language for faster development:
Kotlin Android Extensions
The Android Extensions plugin allows us to get rid from all the findViewById boilerplate code without having to add any extra code or shipping any additional runtime:
Code in Java:
Isn’t it wonderful?
Here is the real power of the language in my opinion, we can easily add utility function to our components from outside and use them seamlessly in our classes, here are some examples that I’ve used in my extension class:
Java in general, and Android in particular, has not so few problems, and although Oracle and Google adding features and trying to keep up the pace- it’s too slow and too heavy handed.
Kotlin is some experiment from JetBrains to bring the latest design patterns paradigms to Java, Android and JS platforms that was quickly take Android community attention (and even inside Google).
As you can see it look pretty good for start, it can save much redundant code and speed up development, and it will be interesting what will be next moves from Google and JetBrains and if it gonna get to the mainstream.
Originally published at shem8.github.com on January 1, 2016.