Hand-curated Kotlin Multiplatform news, deep dives & tools — weekly

It's for working engineers building with Kotlin Multiplatform: Android developers moving into multiplatform, iOS engineers sharing logic via KMP, and tech leads evaluating KMP and Compose Multiplatform for their teams. If you ship (or want to ship) KMP in production, it's written for you.

No, but it helps to be comfortable with Kotlin. It's written for practising developers, so we cover real topics like architecture, dependency injection, persistence, and Compose UI rather than "hello world." Newcomers are welcome; if you're brand new, start with our KMP Guide first.

Every Tuesday issue runs through the same eight sections: a short intro, The Log (the KMP/CMP news that actually matters), The Main Thread (the best community threads), Expect Actual (a technical deep dive), LazyColumn (Compose tips and snippets), The Dependency Graph (curated libraries and tools), Target: Production (real-world KMP apps), and Careers (KMP jobs). Read a recent issue → Kotlin Multiplatform Newsletter #18

All of it. Android and iOS are the core, but we also cover Kotlin Multiplatform on desktop, web, and the server, plus Compose Multiplatform for sharing UI - including Compose on iOS. "KMM" was the old mobile-only branding; today it's all just Kotlin Multiplatform, and so are we.

Once a week, every Tuesday. We respect your inbox — no mid-week "breaking news" blasts unless it's something genuinely urgent, like a critical Kotlin security patch.

Yes, completely free, and it always will be. The goal is to grow the Kotlin Multiplatform ecosystem by making the best news and resources easy to find. It's funded by occasional, clearly-marked sponsors, not by paywalling readers.

No. One email every Tuesday, that's the whole deal. No drip sequences, no daily blasts, and we never sell or share your address. Every issue has one-click unsubscribe, no hard feelings.

Because the official channels cover what JetBrains ships; we cover what the community builds with it. Each issue is hand-picked: real-world case studies, third-party libraries and wrappers, Compose Multiplatform experiments, and the Swift-interop gotchas you won't find in release notes — filtered down to the few things worth your time.

Every link is personally vetted by Bogdan, a senior software engineer with 8+ years in mobile and multiplatform development. No AI-generated filler and no automated link dumps, just one practitioner reading the whole ecosystem so you don't have to.

Yes, every issue has a Careers section with curated Kotlin Multiplatform roles, from KMP/Compose mobile positions to multiplatform architecture jobs. Hiring for a KMP role? You can submit it to be featured.

Yes, and we'd love that. If you've built a KMP/CMP library, written a deep dive, or shipped a production app, submit your link! Community submissions are a big part of what makes each issue worth reading.

Yes, a limited number of sponsor slots are available each month for tools, products, and job posts that genuinely help KMP developers. See the sponsorship page for formats and availability.

No, commonMain.dev is fully independent. That's deliberate: it means the curation is unbiased, with no vendor agenda about which tools or approaches get covered. We just recommend what's genuinely good.

Yes. KMP has been stable since late 2023 and runs in production at companies like Google, McDonald's, Netflix, and Forbes. Our Target: Production section showcases real-world KMP apps in every issue, and our KMP Guide covers the maturity story in depth.

For most Kotlin and mobile developers, yes. KMP lets you share business logic (and with Compose Multiplatform also UI) across Android, iOS, desktop, and web while keeping native performance, making it one of the most in-demand cross-platform skills right now. The KMP Guide is a good place to start.

Kotlin Multiplatform (KMP) shares non-UI code (business logic, networking, data) while you keep each platform's native UI. Compose Multiplatform (CMP) is built on top of KMP and lets you share the UI too, using Jetpack Compose across Android, iOS, desktop, and web. Use KMP for logic; add CMP when you also want shared UI.

The big difference is flexibility. Flutter and React Native ask you to rebuild your UI in their framework; KMP lets you share as much or as little as you want — logic only with fully native UI, or shared UI via Compose Multiplatform — all in Kotlin with native performance. The KMP Guide breaks down the trade-offs.