For the first one, it’s so simple in Kotlin it doesn’t really add much boilerplate. We have a couple of extra things, however, that Butterknife provides, such as onClick and resources binding. So that way, we are saving all the lines. Nick decided to use Butterknife to recover views, which is an excellent solution for Java code, but Kotlin provides Kotlin Android Extensions, which automatically binds them to the activity. It’s quite big, so not sure if I’ll find the time (or the need) to do it. My first disclaimer is that, though it may happen or not, my main goal is not converting the whole App to Kotlin. I just converted HomeActivity and wanted to compare the resulting code, what things are drastically improved and, of course, give you access to the code so that you can extract your own conclusions. And what a better way than rewriting the App into Kotlin? So, after testing Plaid, the app developed by Nick Butcher, and being marvelled about the awesome look and transitions of the App, I wanted to know more about it. Explaining a lot of abstract features without putting them into context is not always the best way to tell about the goodness of a language. The thing is that I never directly converted an Android App from Java to Kotlin, so it’s always a difficult question to answer.

People often ask me about the advantages of writing Android Apps using Kotlin.

Warning: The Plaid project has changed a lot since I wrote this, but here there are still some useful ideas that can help you in your own projects to start thinking the “Kotlin” way

Converting java to kotlin