kotlin-multiplatform-expect-actual

Use expect/actual declarations or common interfaces to separate commonMain APIs from platform-specific implementations, ensuring a single stable call site. This prevents platform specifics from leaking into shared code.

Use expect/actual versus common interfaces in a Kotlin Multiplatform module based on your dependency structure and interop needs. Expect/actual provides direct platform bindings, while common interfaces offer flexible dependency injection across Android, iOS, Desktop, and Wasm modules.

Define expected APIs in commonMain and provide actual implementations in platform modules. This strategy maintains stable cross-platform boundaries for permissions, files, settings, and sensors across Android and iOS.

Yes, you can use expect/actual for interop scenarios involving permissions and sensors across Android, iOS, Desktop, and Wasm. This approach structures platform bindings and module dependencies to maintain stable call sites for these platform-specific features.

Limitations of using expect/actual for platform boundaries in Kotlin Multiplatform include strict matching requirements between expected and actual declarations and potential module dependency complexity. Consider common interfaces for more flexible dependency binding across platforms.