My approach to handling of Android Fragment lifecycle. It's the only way I can use Fragments and still keep the complexity manageable and my sanity intact.
My very troubling thoughts about the future of Android.
I performed an extensive research to understand what's Oracle vs. Google lawsuit all about. In this post I'll share several facts that I discovered along the way that shocked me personally.
My analysis of the reasons that might've led Google's to officially support Kotlin programming language for Android development.
My approach to handling of Android Activity life-cycle. This is probably the easiest yet safest way to accomplish this non-trivial task.
The most important lessons I learned by producing, publishing and promoting my first course on Udemy platform.
My thoughts about Data Classes, which I consider to be the best Kotlin feature. Not because Data Classes spare lines of code, but because this construct has the potential to fix a long standing misconception about object-oriented design.
I came up with a simple design rule related to Context objects in Android that makes my code more readable and maintainable.
Testing that Android apps support save & restore flow is not easy but absolutely mandatory. Let me show you how I do it.
Android apps design and architecture must explicitly account for the core memory management mechanisms inside Android OS described in this post.