I have introduced some common utilities in [part I] here are are some more that you can use everyday. I have made them extension function on fragment , you can convert for activity if you want. Easy Way to show a loader Most of time I see developers adding a LottieAnimationView in all screen a setting…

In the previous article we flew some jets to fight our enemies , in this article we will focus how to defend our country from enemies so we will create a radar to detect enemy jets. note: you may need knowledge of canvas drawings in android as prerequisites for this…

Below are some utility functions that are very common I created them as extension functions to make them more shorter and natural. I believe they can save you a lot of time and make your code short and more readable so just put them In a file and use in…

In this Article we are going to fly a plane or the screen Path() Path is an android class it is very useful or many time only choice in android for creating arbitrary shapes and drawings arbitrary figures , Path is also used in animations. But often times working with paths…

Although this article is independent but I will encourage to read the [Part I] if you haven’t already because their I am also taking about essence of these functions. joinToString() joinToString() is used to convert a collection to a string this method takes prefix ,postfix, separator etc as optional arguments, read…

Below are some functions that can make your life a-lot easier as a programmer because almost all programmers find use cases for these functions very often but because they just don’t know about their existence they take the hard way , which usually is error prone , lengthy , time…

In this create we will create a custom bottom navigation which will look like as it is shown below, there a many complex animations going on which does not exist in the predefined bottom navigation bar.

As you may know that a composable function is restartable means it can be executed many times and any time by the compose runtime. But recomposing entire screen for a small change is not good for performance because of that compose framework has mechanisms to skip recomposition of some composables…

In Compose you can clip a Composable to any shape. The framework provides some predefined shapes like CircleShape, RoundCornerShape, CutCornerShape etc. But what if you want some other shape that does not exist in the framework for example a Pentagon ?. So what do you do when something does not…