Nine years, one operating principle

My background starts with deep native Android development. Java and Kotlin, hand-built UI components, REST integrations that taught me what makes an app feel solid instead of merely functional. From there I moved into Kotlin Multiplatform and Compose Multiplatform, sharing business logic across platforms, then into native iOS with Swift and SwiftUI, and into Flutter, where one codebase had to carry both the UI and the logic underneath it. Somewhere along that path I picked up enough backend and API work to understand how the mobile layer actually talks to what's behind it.

The constant across all of it has been the same. Take a complex, high-traffic mobile system, find the bottleneck or bug that's actually causing the pain, and rebuild the architecture underneath it so the fix holds. Code maintainability isn't an afterthought for me, it's the default: layered architecture, clear ownership boundaries, interfaces that don't leak implementation details.

It also means test-driven development where it actually earns its keep, and cross-platform efficiency that never costs native performance. I share logic through KMP or Flutter where it genuinely cuts duplication, and keep the platform-specific layer native enough that users can't tell the difference. More recently that's extended to agentic AI-driven workflows — using modern AI tooling to move faster without lowering the bar on review rigor or architectural discipline.