Implementing Clean Architecture in Kotlin Multiplatform (KMP) requires a robust data layer that abstracts complexity away from the UI. When adding GraphQL into the mix, the challenge lies in maintaining strict separation of concerns while leveraging the power of the graph across Android and iOS. This lightning talk explores architectural patterns for integrating Apollo Kotlin directly into the commonMain source set.

We will examine how to treat the KMP shared module as the authoritative source of truth, ensuring that platform-specific UIs remain purely reactive.

Takeaways

Shared Normalized Cache: Leveraging Apollo's cache within the shared Data layer to provide a unified, offline-first source of truth that keeps Android and iOS states perfectly synchronized.

Schema-Driven Modularity: Strategies for isolating generated GraphQL network models within the Data layer and using mappers to expose pure Domain entities, preventing API details from leaking into business logic.

Type-Safe Error Boundaries: Implementing a unified Result wrapper pattern that intercepts GraphQL partial failures in the Shared Repository, translating them into clean Domain states for safe UI consumption