Background task execution has always been a topic of discussion in the realm of Android development and there are so many ways to achieve that but that’s a thing for some other time.

There are a lot of articles on memory leaks and how to fix them. But when I was learning myself, I found that none of them were in one place and it was hard to keep track of it all. So I thought I would collectively post an article on it so that it might help people in the future.

MVVM architecture with almost all Jetpack components, Dagger2, Retrofit & a few other libraries a few ground rules which everyone follows or should follow. So, I’ve tried to accumulate some as per my understanding.

As you may experience, there are some scenarios in which applications need to store sensitive data on the user’s device. e.g., JWT for rest web services or user’s data in offline apps (e.g., user’s authentication/authorization in the app). Let’s see how can we protect our data from malicious users!

Model–View–ViewModel (MVVM) is a software architectural pattern which facilitates separation of development UI (Activity or Fragment) from the development of the business logic or back-end logic (the data model).

Modular app development got more trendy this year at google IO 2019 (Yigit Boyar and Florina Muntenescu had a great talk I encourage you to watch it). Additionally Android architecture components have become an inseparable part of native android development and more and more developers start using it.

LiveData is an observable data holder, part of the Android Jetpack.

Let’s say that you want to pre-populate your database with data either packaged in your APK or downloaded from the server. Whether you wanted to do this with SQLite or with Room, there are several things to handle: opening the database, validating the schema, locking the database file and handling thread synchronization, copying all the contents and closing the database.

A lot of automotive companies are currently exploring the possibility to lock and unlock the vehicle, as well as to start the engine via smartphone without the physical key. However, the existing implementations of the digital key seemed to us not very convenient for the end-users.

Before you start writing your code, it’s better that you understand how to manage your code and how to make your code scalable.