It was 2015 January, Janishar Ali and Amit Shekhar(me) started the Android Development. As both of us are Civil Engineer graduate. We learned to code from the internet where everyone is very supportive. We learned almost everything from the internet. Then it was time to give back to the community so we started sharing our knowledge through videos and blogs. In this post, we are going to share the ultimate learnings which we learned the hard way during our journey.
It all started when I was devoid of any projects at work. I planned on developing a very simple offline dictionary app. First things first, there needed to be an efficient search page, because dictionaries are, you know, BIG! It was time to design the perfect auto-complete search UI.
The year 2018 saw a lot of big changes in the Android World, especially in terms of Android Networking. The launch of a stable version of Kotlin Coroutines fueled a lot of movement from RxJava to Kotlin Coroutines for handling multithreading in Android.
When you think about API monitoring, you think about complex tools and fancy dashboards. But sometimes you don’t need to start that big.
As a user you expect a mobile app to work. As developers, we want to make sure of this. As mobile developers, we can control what happens on the device. But most apps rely on an API. This is where the content comes from. And a lot of things can go wrong on that journey.
Here’s an interesting find, I came upon recently. In the the process of moving an Android app project of mine, Camverter, off the now ageing version r10e of the Android NDK and onto version r18b, I had to rebuild some of its dependencies as well, in order to to maintain standard library compatibility.
A few posts out there guide us to test Coroutines. The issue is that many posts where written before the API became stable, so before the scoping changes that happened. Also, I did not find many tips about mocking and Coroutines. Time to fill this gap.