Sharing and Separation — Design Guidelines for Production Adoption of Compose Multiplatform

Kotlin Multiplatform (KMP) lets you share network communication and domain logic between Android and iOS, while Compose Multiplatform (CMP) further unifies the UI layer. Combining the two enables you to develop most of an app in a single codebase—a major attraction. However, once you step into a real product, “non-shareable areas” inevitably emerge because: - The library or SDK you want to use is not KMP-compatible - You need to call OS-specific APIs directly - You want to craft some screens with rich native UI In this session, Android and iOS engineers will co-present: - Which parts of the code should be shared and which should be separated between platforms - Design and implementation patterns that balance development speed with user experience All topics are illustrated with concrete examples from a product that adopted CMP and released both Android and iOS apps in just under six months. Planned topics: - Front lines in sharing How far you can unify code by leveraging CMP + KMP-ready libraries - Separation techniques - DI design across Kotlin × Swift - Safe integration of SDKs that do not support KMP - Hybrid implementations of CMP + native UI - Pitfalls and workarounds viewed from both platform perspectives We will share guidelines for identifying the “non-shareable” areas you will inevitably encounter when adopting CMP and for isolating code where necessary. (Translated by the DroidKaigi Committee)

• Kenta Enomoto STORES, Inc.

• 

  naberyo STORES, Inc.