I'm a Senior Android Developer based in Surat, India, with 5+ years of professional experience building mobile apps in Kotlin, Jetpack Compose, and Compose Multiplatform.

I work at a product-based company, where I split my days between shipping features, reviewing code, mentoring teammates, arguing productively in architecture discussions, and occasionally explaining for the hundredth time why we don't put business logic in Activities.

I care about the stuff that doesn't make it into tutorials: graceful offline states, cold-start times, crash-free sessions, and the specific joy of deleting 400 lines of legacy code in a single PR.

Kotlin is my daily driver. Jetpack Compose is how I build Android UI, and Compose Multiplatform is how I take that same UI across platforms when the product calls for it.

I architect with MVVM + Clean Architecture, inject with Hilt (and Koin on the KMP side), persist with Room, and talk to APIs with Retrofit + OkHttp (or Ktor when I'm in multiplatform land).

I've shipped enough Play Store releases to have strong opinions about release notes, and I pair Claude Code into my workflow because writing boilerplate is not a personality trait.

Because writing the same login screen three times in three languages is exactly the kind of work that makes developers age prematurely. CMP lets me share real UI — not just business logic — across Android, iOS, and desktop, without the "looks like a web page in a trench coat" feel of older cross-platform tools.

It's not a silver bullet for every product, but when the fit is right, it's the most exciting thing to happen to mobile development in years.

• Turning fuzzy product requirements into shippable architecture
• Code reviews that actually teach, instead of just leaving 🚨 emojis
• Mentoring mid-level devs into senior ones
• Pragmatic technical decisions — the goal is shipped software, not architectural perfection
• Owning features end-to-end: design reviews, implementation, rollout, post-launch fixes

Most of my production work lives inside private codebases, so I can't name the apps — but here's the flavor of what I've built and led:

• Migrated a large Android app from Java + XML to Kotlin + Jetpack Compose incrementally, without freezing the release train.
• Rebuilt a core user-facing flow in Compose that shaved cold-start time and cut crash rate noticeably on low-end devices.
• Architected offline-first features using Room as the source of truth, so the app stays usable on bad networks (which, for a product serving an Indian user base, is most networks).
• Integrated monetization (AdMob, subscriptions) without tanking retention — the part most guides skip.
• Introduced Compose Multiplatform into an existing Android codebase to start sharing UI with iOS.
• Mentored 3+ mid-level Android devs through the Java→Kotlin and XML→Compose jump, via pairing, reviews, and internal docs.

Happy to walk through any of this in detail over a call.

An all-in-one webmail app for Android — one app, many providers, each opening in its own isolated webview session. Tap Gmail, you're in Gmail. Tap Outlook, totally separate session. No account mixing, no cloud sync middleman, no accidentally emailing your boss from your personal address.

The constraints are what make it interesting: no push notifications, no cross-provider search, no server in the middle. Just a fast, privacy-respecting wrapper that treats your inbox like yours.

Both remote senior mobile roles and freelance projects — Android, or Compose Multiplatform if you want to go cross-platform. I'm a strong fit if you need:

• A senior IC shipping Compose-first Android code
• A Compose Multiplatform build taken from prototype to production
• A legacy Java/XML Android codebase migrated to Kotlin + Compose without a year-long rewrite
• Monetization (AdMob, subscriptions, IAP) done cleanly
• Someone who'll have a working build by Friday, not a 40-page spec by quarter's end

• Jetpack Compose gotchas nobody warns you about
• Compose Multiplatform — when it's the right call, when it isn't
• AdMob and subscription strategies users don't hate
• Claude Code for Android workflows
• Why Surat's tech scene punches above its weight

_{⚡ Fun fact: "Hilt" and "Room" sound like they belong in a Tolkien novel. I will die on this hill.}