1. Neruromorphic ProgressBar



Documentaion and Other Sources

Youtube Channels

  • CodingWithMitch : Learning to code by making real Android projects.
  • Phillip Lackner : Since the development niche is evolving so fast, I will help you to keep track of it so you don’t feel lost in the jungle of coding.
  • Android Developers : Official Channel for Android


  • Android Apprentice – Android Apprentice is the book for complete beginners to Android development.
  • Programming Android with Kotlin – This book helps Android developers make the transition from Java to Kotlin and shows them how Kotlin provides a true advantage for gaining control over asynchronous computations.
  • Data Structures & Algorithms in Kotlin – A book that teaches you the fundamental tools of implementing key data structures in Kotlin, and how to use them to solve algorithms.
  • Elements of Android Jetpack – This book follows in the footsteps of The Busy Coder’s Guide to Android Development, to introduce developers to Android app development, focusing on Jetpack. Here you will learn how to set up an Android app for Java or Kotlin, create a user interface, and more!
  • Advanced Android App Architecture – In Advanced Android App Architectures, you’ll find a diverse and hands-on approach to architecting your apps on Android. Learn how to build scaleable and maintainable architectures in Android and Kotlin, including MVC, MVP, MVI, MVVM and VIPER!


Android Best Practices

Clean Code

  • Clean Code is one which is easy to read, change, maintain and follows the DRY (Don’t repeat Yourself) principle

General Rules

  • The code structure should be well formatted.
  • The code should follow the DRY Principle.
  • All the classes and functions should exhibit their individual functionality.
  • Introduce modules in your app.

Naming and Comment Principles

  • All the names in the code should be clear and meaningful.
  • Do not add unnecessary and redundant comments in the code.
  • The comment should be used to clarify the respective piece of code.

Formatting Rules

  • The files should be consistent and not very long.
  • Files should have headings to explain the purpose of the file.

Classes and Functions

  • Generally, all the classes should have separate files.
  • Classes and Functions should be too the point.
  • Keep the number of arguements in the function to minimum.

For more information

  • Refer to the book by Robert C. Martin aka Uncle bob – Here
  • Or Refer to his video lectures on Youtube – Here


View Github