How android/kotlin-multiplatform-samples works
Project Type and Purpose
• Fruitties is a Kotlin Multiplatform mobile application sample.
• It demonstrates sharing business logic (network, database, view-model) between Android and iOS clients.
• Mobile clients fetch fruit data over HTTP (Ktor), cache it in a local DB (Room/SQLDelight/DataStore), and render it in native UIs (Jetpack Compose and SwiftUI).
File Structure
• Top-level modules:
• androidApp/ – Android client (Kotlin, Compose UI, Hilt/DI).
• iosApp/ – iOS client (SwiftUI app entry, views, DI bridge).
• shared/ – Kotlin Multiplatform module:
– commonMain/ – shared business logic (models, repository, API interface, ViewModel, DB definition).
– androidMain/ – Android-specific DI & manifest.
– iosMain/ – iOS-specific DI & ViewModel owner.
• Build scripts and Gradle KTS configuration for KMP.
• Database schemas under shared/schemas for SQLDelight or Room codegen.
• Network interface FruittieApi.kt using Ktor client.
Readme Insights
• “Sample app using Kotlin Multiplatform ViewModel, Room, DataStore and Ktor to fetch, store and display data.”
• Purpose: demonstrate common code reuse across platforms.
Main Components
a. Android App
– UI layer (MainActivity, ListScreen)
– DI container (App.kt)
– Platform adapter hooking into shared ViewModel
b. iOS App
– SwiftUI views (ContentView, CartView)
– DI/ViewModel owner (IOSViewModelOwner)
c. Shared Module
– ViewModel (MainViewModel)
– DataRepository
– DataSources:
• Remote: FruittieApi (Ktor client)
• Local: AppDatabase (SQLDelight/Room Dao) + CartDataStore (DataStore)
– Models (Fruittie, FruittiesResponse)
– DI container (AppContainer, Factory implementations)
d. External Services
– Remote REST API endpoint (HTTP server)
Relationships and Data Flow
• UI (Android/iOS) → ViewModel (shared)
• ViewModel → DataRepository
• DataRepository → [Remote API via Ktor] and → [Local DB/DataStore]
• Local DB/DataStore → cached data back to ViewModel
• ViewModel → UI updates
Architectural Patterns & Principles
• MVVM (View → ViewModel → Model/Data)
• Clean separation of concerns: UI, DI, business logic, data sources.
• Shared “commonMain” for platform-agnostic code; “androidMain”/“iosMain” for platform specifics.
• Dependency Injection via AppContainer/Factory pattern in shared module, with platform overrides.
Technologies & Frameworks
• Kotlin Multiplatform
• Ktor (HTTP client)
• SQLDelight or Room (local DB)
• DataStore (preferences/cart storage)
• Jetpack Compose (Android UI)
• SwiftUI (iOS UI)
• Gradle KTS for builds
• DI via simple Factory/AppContainer pattern
Final Checklist
• [ ] Clear module boundaries (androidApp, shared, iosApp).
• [ ] Labels specifying technologies (Ktor, SQLDelight, Compose, SwiftUI).
• [ ] Notes on DI pattern (AppContainer, Factory) and platform overrides.