Scaling Shredzilla: Slaying Memory Leaks & Mastering State in Jetpack Compose

Building a fitness app is easy. Building a production-ready , offline-capable, memory-efficient fitness app that survives Android's brutal lifecycle changes? That's a different beast entirely. Over the past few weeks, I’ve been heavily refactoring my open-source workout tracker, Shredzilla , moving it from a "working prototype" to a rock-solid, production-ready architecture. In this article, I want to share the critical architectural lessons learned during the v1.1.0 Refactoring Sprint , how we solved some nasty memory leaks, and what’s coming next in the v1.2.0 Performance Update . What We Achieved in v1.1.0: The Great Refactoring Version 1.1.0 was all about Stability, Security, and DRY Principles . Here are the biggest wins: 1. Slaying the Eternal Firestore Memory Leak 🧛‍♂️ If you use Firebase Firestore's addSnapshotListener , you might be leaking memory without realizing it. Previously, Shredzilla's listeners stayed alive in the background even after a user logged out, consuming mem