SlothieSmooth

A blockchain may be considered as a digital database, since it saves data digitally. Due to the immutability of blockchain data, it has the potential to revolutionize fields such as finance, security, and medicine. These are just few which are noted here. Overview To begin with, Let’s define blockchain technology first. Using decentralization and cryptographic hashing techniques, blockchain technology, also known as distributed ledger technology (DLT), ensures that the transaction history of any digital asset cannot be altered and is completely visible....

Openness of Android makes it very delicious target for the exploiters, reverse engineers. Android offers a very nice advantages for malicious actors which are not available in compare to its rival iOS. It is possible to peek into the source code when it comes to Android (Yes, I am talking about AOSP) and modify the OS and all the things come along according to your taste. Even in retail devices, It is possible to tamper with the system without much hassle and headache....

Overview The design thinking in a nutshell is the practice of thinking like a designer. It is also considering user desirability, technical feasibility, and commercial viability. All these technical terms might overwhelm you, But once you get a hang of it, It is easy to follow along. The design thinking processes follow a simple format Empathize with your users. Define user needs and problems. Ideate solutions. Prototype your ideas. Test your prototypes....

Overview Using suspend methods with coroutines is a new norm while using Kotlin in Android, Kotlin Native or Kotlin Multiplatform. Recently, I have been searching good libraries for the multiplatform for a pet project I am working on, and I have seen many libraries and implementations that uses GlobalScope as coroutine scope. This is a huge antipattern because using GlobalScope can lead to memory leaks. Problem with GlobalScope Though in Android, using suspend methods is fairly easy because you can just use viewModelScope because most of the heavy lifting is being done inside viewmodels....

Overview Logs are very useful while debugging an issue and finding a root cause for it. I would write tons of garbage logs lines such as “inside save image method”, “user clicked on button send” or something like “image-Id=83488131". I would delete all these stuff as soon as I know what is the issue, and ready to commit changes. But, having too much verbosity in logs is equally bad and pollutes the log cat....