Kotlin Census 2018

Our Kotlin community is growing fast; the number of users has increased by almost 3 times this year. The feedback you give is very important to us both as newcomers who have just started using Kotlin in 2018 and as experienced Kotlin users.

If you’re still hesitant about using Kotlin, we would like to know why. Your responses are very appreciated and important to us too.

If you filled out the survey last year, thank you! To make sure we are keeping our information up to date it would be really helpful for us if you could, please, do it again this year. We’ve added a few new questions and modified the options available to respond with based on the last year’s results and the new technologies which have appeared in 2018.

Please, could you kindly give us five minutes of your time and fill out the following survey.

Thank you!

By providing us with your details, this is not automatic consent for us to use your name, application, or company name. Your information is kept strictly confidential. We will always ask for written confirmation from you before we would ever try to use it.

About Alina Dolgikh

Kotlin Community Manager
This entry was posted in community and tagged , . Bookmark the permalink.

12 Responses to Kotlin Census 2018

  1. Nathan Williams says:

    Survey complained about incomplete entry without stating what was missing, then expected me to start over. (Safari iOS)

  2. Oleg says:

    When I accidentally chose “I don’t know” in the list of supported Android versions, it didn’t let me change the selection anymore.

    • Alina Dolgikh says:

      Hi! Sorry about this, I’ll look into it. Thank you for reporting the issue and let me know if you need any assistance.

      • Alina Dolgikh says:

        Hey, I’ve investigated the issue. Please, to do so click one more time on ‘I don’t know’ this will uncheck the checkbox. Then you can make another choice.

  3. Abdullah khalid says:

    I think there should be a video lectures on RxKotlin !!!

  4. Just wanted to point out that inline classes (release in 1.3, but comments closed for that post) don’t seem to work with the Parcelize implementation.

    Is this a known issue by chance?
    Would be great if these were compatible. Tried using custom Parceler as both a companion class and separate class with @WriteWith/@TypeParceler attributes, but none of the approaches worked.


  5. Absolutely loving this!! Looking forward to growth in the global Kotlin community.

  6. kotlinFan says:

    Will the results be published?

  7. Louis says:

    I can’t wait for the final report !

Comments are closed.