Divyansh Kushwaha’s GSoC 2022 Report

5 min readOct 6, 2022

Name: Divyansh Kushwaha
Organization: AnkiDroid
Proposal: Divyansh’s GSoC Proposal
Objective: AsyncTask to Coroutines Migration Issue #7108

Hi! I am Divyansh, and I’ve finally completed my Google Summer of Code 2022 project under the mentorship of the organization AnkiDroid

What is AnkiDroid?

AnkiDroid is an Android companion app for Anki, a flashcards application that helps people learn and memorize a diverse variety of topics.

AnkiDroid: Anki flashcards on Android. Your secret trick to achieve superhuman information retention.

The first interaction with maintainers

My first interaction with a maintainer happened accidentally. I was working for a startup that used a fork of AnkiDroid as the base of their project. I had to remove the sync feature from the existing fork and I mistakenly made a pull request to the main AnkiDroid repo 😆(kind of felt funny, but yeah this was it). So my first PR was an accidental one and was closed unmerged. David Allison was the first to comment on that and asked me to share a link to the project, so I joined the discord server. And that was the beginning of me starting my contribution to AnkiDroid. There I saw a separate channel for GSoC, and since I was looking to apply for it I started asking questions on the server and found the community very welcoming and helpful. From there my journey to open-source contributions began.

Initial Contributions

After joining the discord server, I came to know that there is something called good first issues which is for newcomers to get familiar with and start their contributions. During that time, AnkiDroid was going through Java to Kotlin migrations. There were some changes that would reduce and simplify code using Koltin features, such changes were marked as KotlinCleanup. Before starting GSoC I started with these cleanup tasks. And eventually started working on the migration of startActivityForResult to newer APIs. Done a few KotlinMigrations myself as well.

Objective

AnkiDroid was initially built on Java and used AsyncTask to handle asynchronous operations. Since AsyncTask is deprecated and AnkiDroid was already migrating to Kotlin, the asynchronous operations such as network calls, database access, etc can be moved to Kotlin Coroutines. I already wanted to learn more about concurrency and parallelism concepts.

So, the Migration from AsyncTask to Coroutines was the objective of my GSoC project.

Application for GSoC

After choosing the GSoC topic and getting familiar with the codebase, it was time to prepare my proposal. For that, I really needed to put together strategies that I could use to do the migration. After going through these all, I did a sample migration just to show what the actual project might look like. I wrote the Application from the standard template that was provided by the organization only. I asked for a review of my Application by maintainers and received a lot of them. It went through 3–4 rounds of review till I finally submitted my proposal.

Community Bonding Period

It is the initial time that Google gives to involve in the community activities that happened within an organization. Since I already had been contributing and knew the community it went very well, even though I started my coding in this period. I had a video call meet together with the other community members and my fellow GSoC students as well. It was a fun session and we shared our journey and experiences with the community so far.

Coding Period

The first thing to do before starting the migration to Coroutines is to migrate required classes from Java to Kotlin because coroutines are a Kotlin feature. During the first week, I worked on migrating existing Java files that contain AsyncTask codes to Kotlin. I utilized my this time well by doing many Kotlin migrations. Thanks to the automated script that we have in AnkiDroid which made this process a lot easier. For migration to Kotlin, we followed a specific set of rules to make sure nothing breaks and the transition is smooth (like avoiding functional changes). More detailed documentation is written by community members which can be found here.

For the coroutines, my initial plan was to create a base wrapper class similar to AsyncTask but instead of using underlying raw threads I would use suspend functions for the callbacks. I thought that migration should be done without changing the already existing architecture, like a patch on existing code but after discussing with the mentors and other community members I came to a conclusion to follow a different approach. Most of the architecture was laid down to handle cancellations and memory leaks due to AsyncTask which we do not need to worry about when using Coroutines. Using the right CoroutineScopes and bounding the coroutines to a LifecycleOwner handle these two very well, so we do not have to worry about checking if the UI is still alive or not.

Following a strategy, the doInBackground callback of AsyncTask would be replaced by a suspend function performing the same operation. And onPreExecute and onPostExecute callbacks would be called as it is before and after calling the suspend function. Using this concept, I started migrating firstly with the independent classes, and later when I became much more familiar with the codebase I started migrating the core part of the codebase.

List of merged PRs in which I’ve done the migrations:

After the migration, I realized that I have completely deviated from my initial plans but for good. Migrating with the newer approach made the codes much cleaner and easy to follow.

Final Results

Since my changes do not include UI changes, I don’t have anything visual to show but my work is clearly visible through my pull requests. Although I couldn’t complete everything within the given timeline, I can say that most of the migration has been done, and the remaining will be done in the continuation. I’ll also keep contributing to the AnkiDroid after GSoC and will put my efforts to improve the codebase. I would like to thank Shridhar, Arthur, Mike, Damien, Luksbit, David, and all the other folks around the community. You guys are awesome and I’ve had a very good time together with you spending my summer discussing and programming.

AnkiDroid: https://github.com/ankidroid
GSoC: https://summerofcode.withgoogle.com

Learning Outcomes

Before working on GSoC I did not have much experience with Git-GitHub workflow, PRs, Code reviews, coding discussion, planning, having conversations with community members, etc. These are the most valuable things I would say I learned from my GSoC period. Also working on the project I learned Kotlin Coroutines in great depth along with the concepts of AsyncTask, and how Android used to be before Kotlin. I would say GSoC has had a very huge impact on my skills and my experience was awesome.