Many Android apps never make it beyond a few thousand users. Some fail because of poor architecture, some because of unnecessary complexity, and many because they solve problems users simply don't have. Over the past few years, I built a Kannada language learning app as a side project that has grown close to 1 million organic downloads across 100+ countries. As a solo Android developer working full-time, every technical decision mattered—from architecture and feature prioritisation to performance optimisation, analytics, AI integration, monetisation, and long-term maintainability. This talk isn't about marketing hacks or overnight success. It's a practical case study of the engineering decisions, mistakes, and trade-offs that shaped the product over several years. You'll learn: How to make technical decisions that support long-term product growth rather than short-term feature delivery. How analytics and real user feedback can guide engineering priorities. How to balance shipping features, reducing technical debt, and maintaining app quality as a solo developer. Lessons learned from building, scaling, and maintaining a production Android app used by hundreds of thousands of learners. Mistakes I would avoid if I were starting from scratch today. Whether you're building your first side project or maintaining a mature production app, you'll leave with practical ideas you can apply to your own Android applications.