How ricarlo-silva/cmp-app-recipes works
Project type and purpose
• This is a cross-platform mobile application (“CMP App Recipes”) targeting Android and iOS, built with Kotlin Multiplatform and Compose Multiplatform (CMP).
• It separates shared business/UI logic from platform-specific implementation.
File structure
• Top-level modules:
• androidApp: Android UI & entry point
• iosApp: iOS UI & entry point
• shared: Common Kotlin logic & shared CMP UI
• core:
– designsystem: shared UI building blocks
– network: shared HTTP client & networking abstractions
• feature/login: shared login feature
• build-logic: custom Gradle plugins & build conventions
• The dependency graph (shared → core/designsystem + core/network + feature) → platform apps.
README for additional insights
• Uses Compose Multiplatform for UI
• Koin for DI
• Ktor for HTTP
• GitHub Actions for CI/CD
a. Main components
1. Android App (androidApp module)
2. iOS App (iosApp module)
3. Shared CMP Module (shared)
4. Core – DesignSystem (UI toolkit)
5. Core – Network (Ktor client & TokenManager)
6. Feature – Login (business logic & screens)
7. External Services (REST API, Backend)
8. Build & CI (build-logic + GitHub Actions)
b. Relationships & interactions
• androidApp & iosApp depend on shared, core/designsystem, core/network, and feature/login
• shared module composes UI with DesignSystem and invokes network APIs via core/network
• feature/login sits atop shared and core modules, exposing login use-cases to the UI
• Koin runs in each platform app to wire up shared + core modules
• At runtime, network layer (Ktor) calls out to external REST endpoints and returns data back up to UI
c. Architectural patterns & principles
• Modular monolith: multi-module separation by concern (shared, core, feature, platform)
• Dependency Injection (Koin) for loose coupling
• Layered architecture: UI → Feature → Domain (shared) → Network → External
• MPP abstraction: commonMain / androidMain / iosMain sources
d. Key technologies
• Kotlin Multiplatform & Compose Multiplatform
• Koin (DI)
• Ktor (HTTP client)
• Gradle custom plugins (build-logic)
• GitHub Actions for CI/CD
Essential architectural elements to capture
• MPP layering (commonMain vs androidMain vs iosMain)
• Module dependencies (shared ← core/designsystem, core/network, feature/login)
• Platform entry points and DI setup
• Network communication boundary
• Build-time plugins and CI integration