Android Unplugged | Quality Tools for Developers

  As a mobile engineer, you’ve probably seen terms like SHA-1 and SHA-256 pop up everywhere—in your IDE warnings, API documentation, and app signing configurations. But what do they actually mean, and why should you care? Think of a cryptographic hash function as a digital fingerprint generator . You can feed it any data—an entire APK, a user’s password, or a simple string—and it produces a fixed-size string of characters called a hash . This article breaks down what these hashes are, why the old standard SHA-1 is no longer suitable for security, why SHA-256 remains a widely trusted choice, and what newer hashing approaches like BLAKE3 mean for modern developers. TL;DR: SHA-1 is no longer considered secure for collision-resistant applications. SHA-256 remains a strong general-purpose cryptographic hash, while newer algorithms such as BLAKE3 focus heavily on performance and parallel processing. 🔐 Th...

How I built an open-source Kotlin Multiplatform reference project to help Android teams move beyond tutorials and start thinking about production-ready architecture. Last weekend, I had the opportunity to speak at the BlrKotlin x InMobi Android Meetup in Bengaluru, where I shared something I've been working on over the past few months—a practical Kotlin Multiplatform Platform Kit . Rather than giving another introduction to Kotlin Multiplatform, I wanted to focus on a question many Android teams eventually ask once they move past the excitement of "Hello World" examples: "We understand what Kotlin Multiplatform is—but how do we actually structure a project we'd be comfortable maintaining in production?" To answer that question, I built kmp-platform-kit , an open-source reference repository that demonstrates how to organize a Kotlin Multiplatform codebase with clean architecture, modular boundaries, and engineering decisions inspired by re...

Why Memory Leak Detection Shouldn’t Run on Your Device How LeakLens moves Android heap analysis out of the app process and into Android Studio with a dual-layer model of static analysis and runtime inspection. You are in the middle of a refactor, your test device lights up, and a familiar notification appears: 4 retained objects, dumping heap. The report is useful, but the interruption is not. You pick up the device, inspect the notification, try to remember the class names, then jump back into Android Studio to find the source. That debugging loop is exactly the problem this article addresses. The core question is simple: why is the tool that finds memory leaks running inside the same application process you are trying to debug? [page:1] That question became LeakLens , an Android Studio plugin that moves memory leak analysis into the IDE instead of embedding an SDK inside the application. [page:1] Table...

Heap Dumping Explained — Why LeakCanary Freezes Your App to Find the Truth Learn what a heap dump is, when LeakCanary triggers one, why it briefly pauses your app, and how the resulting .hprof snapshot enables Shark to find real Android memory leaks. In the previous part of this series, we explored ObjectWatcher , the component that keeps an eye on destroyed Activities, Fragments, Views, and custom objects. But ObjectWatcher does not prove a leak on its own. It only tells LeakCanary that some objects still look suspiciously alive after they should have been garbage collected. That is the moment when LeakCanary makes its boldest move: it captures a heap dump . Heap dumping is the turning point in LeakCanary’s workflow. It briefly freezes the app, records a binary snapshot of memory, writes that snapshot to disk as a .hprof file, and passes it to Shark for analysis. [page:1] Table of Contents 1. What Is a Heap Dump? ...

Shark Heap Analysis — How LeakCanary Turns Heap Dumps into Actionable Leak Traces Learn how Shark parses Android heap dumps, builds a HeapGraph, traces GC-root paths, filters known leaks, and generates actionable LeakCanary reports. In the previous article, we saw how LeakCanary freezes the app briefly to capture a .hprof heap dump. But a heap dump on its own is only raw binary data. To make it useful, LeakCanary needs an analysis engine that can parse memory records, reconstruct object relationships, and explain why retained objects are still alive. That analysis engine is Shark . Shark is where memory leak debugging becomes understandable. It transforms a raw heap snapshot into a structured object graph, finds the most relevant retaining paths, and produces the LeakTrace reports developers use to fix leaks. Table of Contents 1. What Is Shark? 2. Why Shark Matters 3. Parsing the Heap Dump 4. Building t...

Dominator Tree and Retained Size — Measuring the True Cost of Android Memory Leaks Learn how Shark uses dominator trees and retained size to measure leak impact, prioritize fixes, and explain the real cost of retained objects in Android apps. In the previous part of this series, we saw how Shark parses heap dumps and generates leak traces. But one important question still remains: which leaks should you fix first? Not all memory leaks are equally dangerous. A destroyed Activity retaining an entire view hierarchy can be far more expensive than a small isolated object. That is why Shark uses dominator trees and retained size to estimate impact, not just existence. Table of Contents 1. Why Not All Leaks Are Equal 2. What Is a Dominator Tree? 3. What Is Retained Size? 4. How Shark Uses Dominator Trees 5. Example: Leaking Activity with Retained Size 6. Why This Matters in Real Apps 7. Analyze LeakCanary...

Common Android Memory Leak Patterns — Real-World Traps LeakCanary Catches Learn the most common Android leak patterns, why they happen, and how LeakCanary helps you detect them before they become production issues. In the previous part of this series, we explored how Shark uses dominator trees and retained size to measure the impact of leaks. But theory alone is not enough. To fix leaks consistently, you need to recognize the patterns that show up again and again in real Android apps. This article focuses on the practical leak shapes that LeakCanary frequently surfaces in day-to-day Android development. Table of Contents 1. Why Common Leak Patterns Matter 2. Static Context Reference Leak 3. Anonymous Inner Class Leak 4. Handler and Delayed Work Leak 5. InputMethodManager Framework Leak 6. Fragment ViewBinding Leak 7. Leak Pattern Summary 8. Analyze LeakCanary Reports Faster with LeakLens 9....

Integrating LeakCanary in CI/CD — Automating Android Memory Leak Detection Learn how to export LeakCanary reports, collect them in CI, and turn local leak debugging into an automated team quality safeguard. So far in this series, we have looked at how LeakCanary watches retained objects, captures heap dumps, and uses Shark to explain why memory leaks happen. But in real engineering teams, leaks still slip through when they are only checked manually on local machines. The next step is automation. By integrating LeakCanary into your CI/CD workflow, you move memory leak detection closer to the release pipeline and reduce the chance of shipping avoidable regressions. Table of Contents 1. Why LeakCanary in CI/CD Matters 2. Debug-Build Strategy for CI 3. Gradle Setup 4. Exporting LeakCanary Reports 5. Example CI Script 6. CI/CD Workflow Overview 7. Best Practices 8. Analyze Reports Faster w...