Kotlin Multiplatform makes code sharing across platforms more practical than ever, but things get much harder once a project starts growing. What begins as a clean shared module can quickly turn into a tangled architecture, unclear boundaries, slow builds, and painful dependency management.

In this talk, I’ll share how to approach multi-modularisation in Kotlin Multiplatform in a way that actually scales. We’ll look at how to split features, domain logic, platform-specific code, and shared infrastructure into clear modules without overengineering the project from day one. I’ll cover common architectural mistakes, how to think about module boundaries, how modularisation affects build performance and team productivity, and what trade-offs appear when sharing code across Android, iOS, backend, or web targets.

This session is aimed at engineers who already know the basics of Kotlin Multiplatform and want to move beyond a simple demo setup into something production-friendly. Attendees will leave with a practical mental model for designing KMP projects that stay maintainable as products and teams grow.