How lcdii/energydex works
This is a minimal Kotlin Multiplatform Android/iOS starter, not yet a documented energy-drink workflow. The only visible runtime path is the SwiftUI iOS entry hosting the shared Compose controller. Domain files are present in the tree, but their behavior and connections were not sampled; the graph leaves those links out rather than infer a workflow.
Main entry points: ContentView.swift SwiftUI host · iOSApp.swift iOS app · MainViewController.kt Compose controller
Components 7
Platform entry points
- iOS app
iosApp/iosApp/iOSApp.swift - SwiftUI host
iosApp/iosApp/ContentView.swift - Compose controller
composeApp/src/iosMain/kotlin/com/example/energydeks/MainViewController.kt - Android activity
composeApp/src/androidMain/kotlin/com/example/energydeks/MainActivity.kt
Shared app and domain
- Shared Compose app
composeApp/src/commonMain/kotlin/com/example/energydeks/App.kt - Energy drink model
composeApp/src/commonMain/kotlin/com/example/energydeks/energydrink/domain/EnergyDrink.kt - Domain result
composeApp/src/commonMain/kotlin/com/example/energydeks/core/domain/Result.kt
Connections 2
- iOS app → SwiftUI host: shows
iosApp/iosApp/iOSApp.swift - SwiftUI host → Compose controller: creates
iosApp/iosApp/ContentView.swift