Fragments conducted an online survey with Android developers and teams about Kotlin adoption between March and April 2021. The survey aimed at answering two questions:
- The extent of Kotlin adoption in the Indian startup and enterprise ecosystem.
- How organizations are leveraging Kotlin and its features beyond UI development i.e., whether Kotlin is used for backend engineering and building data pipelines.
Survey respondents were primarily drawn from Android engineers and Android teams in startups, mid-sized organizations and enterprises.
Survey results show that:
Kotlin’s adoption will increase in 2-3 years, with the likelihood that the next generation of entrants in Android software development will be Kotlin native. This will displace Java’s dominance as a programming language for building Android apps.
The results also reinforce that Kotlin is primarily used for UI development. The language’s features and ability for backend engineering is still under-utilized, at least among developers and teams who mainly build Android apps (since the survey respondents are from this demographic).
More importantly, the survey reveals that engineering managers are concerned about moving large Java codebases to Kotlin because of the concern that they will not be able to hire Kotlin programmers and ramp up their teams.
Scroll down to read about the survey sample and detailed findings, and to see the survey questionnarie.
Despite the growing demand for Kotlin and the backing of big tech firms such as Google/Android, there still exist skill gaps in the adoption of Kotlin in India. Kotlin has far-fetched benefits beyond Android as well mainly,
- On the server side, with their interoperability with the Java ecosystem.
- A cross platform mobile and web application development platform through their Kotlin multi platform.
Organizations appear to be reticent in moving their codebase to Kotlin, especially when the codebases are large. This slow move is compounded by the apprehension that hiring Kotlin programmers will be difficult and that upskilling entire teams will be difficult. The current skill gaps likely exist because most developers depend on learning the language by themselves, without access to formal training, and without community forums where experiential case studies about Kotlin can be shared freely.
We conclude that for organizations to make better progress towards adoption of Kotlin, they have to invest in training and upskilling their employees because Kotlin will be the future for Android development.
Bhavani Seetharaman is Research Associate at Hasgeek.
Zainab Bawa is co-founder, director and Chief Operating Officer (COO) at Hasgeek.
Bhavani Seetharaman and Zainab Bawa have written this report. Madhusudhan Sambojhu actively reviewed the report and helped in nuancing the findings and conclusions.
Anish TP illustrated the report.
We would like to thank:
Research methodology and sampling
The survey was conducted online using Survey Monkey. Respondents answered descriptive and multiple choice questions.
We targeted individual developers and app development teams from startups and enterprises to respond to the survey. Respondents from SaaS, Fintech, gaming, mobility, e-governance and IT services domains participated in the survey.
As mentioned in the executive summary, respondents were primarily drawn from among Android engineers and teams. 63 respondents were Android developers. Only two respondents mentioned comfort working with iOS Operating System (OS). Future research needs to examine Kotlin’s adoption and use in the iOS ecosystem.
The survey refrained from asking for personal information to preserve the privacy of respondents. The survey questionnaire instead focussed on the challenges respondents’ faced in using Kotlin, and their organization’s experience with Kotlin adoption. (See Appendix I for the survey questionnaire.)
A total of 65 respondents participated in this survey. Respondents’ organizations either use Kotlin or had considered Kotlin as a choice of language in developing the company’s app.
This sample is a good starting point for further research on Kotlin’s growth and adoption in India for Android and in other domains.
Future research can include more demographic variables such as gender, geographical diversity and respondents from Tier II and Tier III Indian cities so that a larger, diverse sample size can help us understand trends better. The current research is an exploration of the upskilling requirements that the industry faces with the growth of Kotlin for Android.