awesome-sunset-compose-multiplatform

Structure Kotlin Multiplatform code by enforcing clean architecture and strict source-set boundary rules. This approach maintains shared domain logic in commonMain while respecting platform-specific boundaries, preventing over-engineering and ensuring minimal boilerplate across Android and iOS targets.

Manage Compose Multiplatform source-set boundaries by adhering to Kotlin Multiplatform conventions that separate shared application logic from platform-specific UI adapters. This prevents architecture theatre and keeps the unified codebase readable, testable, and pragmatically maintainable.

Refactor navigation logic into commonMain by making small, safe changes that prioritize readability over speculative abstractions. Maintain platform-specific UI adapters alongside the shared implementation to ensure the evolutionary design remains clean and testable.

You need platform-specific source sets in Compose Multiplatform when implementation requires respecting platform-specific boundaries for Android and iOS targets. Evaluate whether logic belongs in commonMain or platform-specific sets to ensure the feature remains clean and testable.

Compose Multiplatform handles testing across Android and iOS by applying clean architecture principles that ensure shared application logic remains testable. Strict adherence to source-set conventions maintains clear boundaries, facilitating effective testing of common and platform-specific code.

Kotlin Multiplatform code becomes over-engineered when architecture theatre introduces speculative abstractions instead of pragmatic, evolutionary design. Enforcing readable implementations with minimal boilerplate and strict source-set boundaries prevents unnecessary complexity in the unified codebase.