Notes from a
lead mobile
engineer.
I write about Kotlin, Jetpack Compose, Kotlin Multiplatform, and the occasional Flutter detour — plus what it actually takes to lead a mobile team without losing the plot. No marketing copy, just what worked (and what didn't).
From the field
Mostly Compose and KMP these days, with the odd leadership post when the code needs a break.
Book Review: Cracking the Tech Career by Gayle Laakmann McDowell
Book Review: Cracking the Tech Career If you've prepped for a coding interview in the last decade, you've probably run into Gayle
Designing an Offline-First Android App: A System Design Case Study
Offline-First Isn't a Feature — It's an Architecture "Add offline support" is one of the most commonly underestimated asks in
Android System Design Interview Questions & Answers
Android System Design Interview: Questions & Answers Android system design interviews reward structured thinking more than a "correct" answer. The questions below are the
System Design Fundamentals for Android Engineers
System Design Isn't Just a Backend Discipline "System design" usually conjures load balancers and database sharding. But a production Android app is
Clean Architecture for Android: Structuring a Kotlin Codebase That Scales
Clean Architecture, Minus the Dogma "Clean Architecture" gets a bad reputation for producing 40 files to fetch a list of users. Used pragmatically, though,
Migrating Android Navigation: XML to Navigation Compose, Then Navigation 2 to Navigation 3
Two Migrations, One Destination Android navigation has gone through three real eras: XML + Fragments, Navigation Compose ("Nav 2"), and now Navigation 3 — a ground-
Hey, I'm the person behind Youdroid.
I lead a mobile engineering team by day and write here by night (well — mostly on weekends, coffee in hand). This blog is where I dump the stuff that doesn't fit in a Slack thread: Compose patterns I keep reaching for, what actually happened when we moved shared logic to Kotlin Multiplatform, and the messier parts of managing engineers instead of just being one.
No sponsored posts, no growth-hacking. Just notes from someone who's still writing Kotlin most days and occasionally still gets paged at 2am.
New posts, roughly every other week
No spam, no funnel — just an email when there's something worth reading.