How nachoarrieta/tvapplicationkmp works
Project type and purpose
• This is a Kotlin Multiplatform “ComposeApp” library + an iOS “iosApp” entry point.
• Targets: Android (via Android SDK), iOS (via SwiftUI host), Desktop (JVM Compose), Web (WASM/JS).
• Purpose: share UI, view-models, data layer, resources across four platforms.
File structure
• Top-level modules:
– composeApp/ (KMP library)
– iosApp/ (SwiftUI iOS wrapper)
• Inside composeApp:
– commonMain/ – shared business logic, models, repository, UI Composables, view-models, navigation, theme, utils.
– androidMain/ – AndroidActivity entry (MainActivity.kt), AndroidManifest, resources (drawables, strings, mipmaps).
– iosMain/ – iOS-specific bridges (MainViewController.kt), Platform.ios.kt.
– desktopMain/ – JVM host main.kt, Platform.jvm.kt.
– wasmJsMain/ – Web host main.kt, Platform.wasmJs.kt, index.html, styles.css.
– commonTest/ – shared tests.
• iosApp folder: Swift/Xcode project, SwiftUI ContentView.swift, Info.plist, asset catalogs – this wraps the Compose library for iOS entry.
README for additional insights
• Confirms KMP targets and folder roles.
• Compose Multiplatform for UI sharing; iosApp is required entry for SwiftUI integration.
• Web launch via Gradle task :composeApp:wasmJsBrowserDevelopmentRun.