Phanindra D

Architecture is the part of the work that survives the people who wrote it — and, done right, the platform it first shipped on. I draw module boundaries so the domain logic doesn’t know or care what renders it, wire dependencies so they point one direction, and pick patterns — Repository, Factory, Observer — only where they earn their complexity. A clean core is portable by construction; the UI framework is the last, replaceable layer.

That conviction comes from a decade on the same product. Running multiple apps from one codebase forces you to be honest about coupling: a shortcut in the data layer becomes four teams’ problem at the next release. So the work is reusable libraries in Nexus, a standardized modular structure, migration to Kotlin and Compose done in slices rather than rewrites, and crash and ANR rates watched like a budget.

The other half is people. I lead a team of six, run the code reviews, and treat mentoring as part of the architecture — a boundary only holds if the engineers maintaining it understand why it’s there. And I’m deliberately widening the surface: Kotlin Multiplatform POCs in production thinking today, and active, honest exploration of the broader cross-platform and native-iOS landscape — depth on Android, reach beyond it.