Hey Community! :raised_hands: JetBrains and I ar...

# android

[Eugene]

Hey Community! 🙌


JetBrains and I are looking for android developers who have something to say about Kotlin adoption for Android development.
1. Please, DM me and share contacts of people who had problems with adoption or even can't use Kotlin in the company because of some reason.
2. Also, if you had problems at the beginning with Koltin, then share what it was using thread (or dm me to keep it private). And please, specify the year/month if possible.

Thanks in advance, and happy coding! ✌️ K

[Eugene]

Example: It was hard to switch from Java to Kotlin because of functional programming. It takes some time to adopt a new style of writing code.

[Chetan Sachdeva]

Migrating from Java to Kotlin couldn’t have been smoother but kotlin-java interop was something.

[henrikhorbovyi]

Migrating from Java to Kotlin was a really awesome experience for me, first time I saw Kotlin I was very impressed how it solved some problems that I had to think for sometime in Java.

Kotlin's syntax is really sexy and it attracted me a lot 😄

But I really dived into Kotlin after the first interaction with the community, I found it very helpful and warm.

That's my feelings about it 🙂

[Yashovardhan]

Being an intern, I am currently working on an app which has a lot of Java and Kotlin code. While almost all new code I am writing is in Kotlin, I have found it difficult to easily convert existing Java code to Kotlin. Almost 65% code is in Java.

Android Studio does a pretty good job at this but for older code which uses a lot of older APIs, it can be a bit hard to refactor.

I have found it hard to decide on choosing/migrating dependencies, since most newer libraries have a separate KTX module.

I personally found it much easier to write code in Kotlin than in Java. Calling Kotlin classes/objects from Java classes can be a bit strange. Like for Kotlin objects, Java will use the .INSTANCE property. Once I even saw a Kotlin file name being appended with Kt when there was no class defined there. (Like ResponseUtilsKt instead of just ResponseUtils.

One person in particular I worked with, wrote code in Kotlin without caring for using any of the newer APIs which make it much easier to work with android. This meant he occasionally took more time doing simpler stuff than was needed.

On the other hand, I have seen companies strictly hiring Java developers for android, not having any interest in switching to Kotlin.

[Joao Birk]

@Yashovardhan to get rid off the .INSTANCE on Java calling Kotlin you can add @JvmStatic to your method. As for the ResponseUtilsKt you can add @file:JvmName("ResponseUtils") at the beginning of the file.

[Yashovardhan]

@Joao Birk thanks a lot!

[Ananiya]

When I migrate from java -> kotlin , I am feeling like removing a lot of load

[brandonmcansh]

It was definitely something interop'ing in the beginning with companion object and JvmStatic use

[deviant]

99% of barriers are due to stupid management and old fashioned thinking tech leads. e.g. "java is here for 30 years and kotlin is just a syntax sugar", "why to learn something new when java just works" etc. i always hear it from old school java devs