How tuanemapero/baseprojectkmp works
Project type and purpose
• This is a Kotlin Multiplatform mobile demo. It ships:
• aiservicekmp – a reusable AI-service client library (remote datasources, models, signature, HTTP client)
• shared – the core business-logic module (domain models, use-cases, repository implementations, local persistence, remote-config, DataStore)
• androidApp – an Android-native wrapper that pulls in shared & aiservicekmp
• composeApp – a Compose Multiplatform UI that targets Android & iOS
• iosApp – an iOS-native shell that pulls in shared & aiservicekmp
File structure
• Top-level modules map to runtime artifacts:
• “aiservicekmp” and “shared” are MPP libraries (commonMain + androidMain + iosMain).
• “androidApp” is a pure Android application.
• “composeApp” is a cross-platform Compose UI application.
• “iosApp” is an Xcode project for iOS.
• Within each MPP library you see:
• commonMain/kotlin/com/... – platform-agnostic code (models, interfaces, DI modules, domain/use-cases)
• androidMain/… – Android-specific wiring (AndroidManifest, HTTP client, DB, signature parser)
• iosMain/… – iOS-specific wiring (HTTP client, signature parser, platform entry points)
• Patterns:
• Clean architecture (DataSource → Repository → UseCase → Presentation)
• DI via Koin (AiServiceModule, ClientModule, RepositoryModule, SharedModuleConfig, ComposeAppModule, ViewModelModule)
• Presentation: MVVM/MVI in composeApp, simple Activity in androidApp
Key takeaways
• 5 modules (androidApp, composeApp, iosApp, shared, aiservicekmp)
• Clean Architecture layering within shared & aiservicekmp
• Platform-specific code boundaries (androidMain vs. iosMain)
• Detail DI flow to tie everything together
• Keep it high-level; avoid drowning in file-tree minutiae, but call out important packages (data.datasource, data.repository, domain.usecase, presentation.viewmodel).