I have been contributing to the tutorials/infographics/podcasts at Kodeco.com (formerly known as Raywenderlich.com) since 2018. I joined them initially as an Author on the Android team, but since then have now jumped into different roles such as being a Technical Editor, a Final Pass Editor, Co-Host for a season of Kodeco Podcast.

Executing tasks and processes is pretty common in the Terminal. Having them run and then pipe the output into another one, transforming the output, triggering a sub-process/task, etc.

TL;DR: I used Google Sheets + Translate + AppScript to build a completely free and robust Automated Android Localization Tool! 🐼 So this started when I found the below tweet:

This isn’t a click-bait article! I will explain how to make your Android build time shorter than the reading time of this post (hopefully) 🏃🏻

Lifecycle events in Android. It has been a pain point for Android developers all over the world. It is no brainer that, most of the times the main cause of a memory leak in the codebase is because an invalid state is accessed which is out of sync with the lifecycle of the activity/fragment of the app.

DISCLAIMER: If you consider yourself a beginner, intermediate, expert or a ninja in the Android realm, this secret sauce still applies to you. TL;DR: Build Something.

It all starts when some android developer tries to figure out a solution to a problem he/she is having while building their “Awesome Android App”.

While working on various projects, there have been times when I have had to implement various gesture-based events. Every time I have had to do that I had to write the whole code for getting the SensorManager and getting access to the SensorEvent, plus the extra logic to detect the gesture.