316b1f709d
Fails CI if any future VM regresses to the pre-migration pattern of owning independent MutableStateFlow read-state. Two assertions: 1. every_read_state_vm_accepts_iDataManager_ctor_param Scans composeApp/src/commonMain/kotlin/com/tt/honeyDue/viewmodel/ and requires every VM to either declare `dataManager: IDataManager` as a constructor param or be in WORKFLOW_ONLY_VMS allowlist (currently TaskCompletion, Onboarding, PasswordReset). 2. read_state_flows_should_be_derived_not_independent Flags any `private val _xxxState = MutableStateFlow(...)` whose field-name prefix isn't on the mutation-feedback allowlist (create/ update/delete/toggle/…). Read-state MUST derive from DataManager via .map + .stateIn pattern. AuthViewModel file-level allowlisted (every one of its 11 states is legitimate one-shot mutation feedback). Paired stub in commonTest documents the rule cross-platform; real scan lives in androidUnitTest where java.io.File works. Runs with ./gradlew :composeApp:testDebugUnitTest --tests "*architecture*". See docs/parity-gallery.md "Known limitations" for the history of the Dec 3 2025 partial migration this gate prevents regressing. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This is a Kotlin Multiplatform project targeting Android, iOS, Web, Desktop (JVM).
-
/composeApp is for code that will be shared across your Compose Multiplatform applications. It contains several subfolders:
- commonMain is for code that’s common for all targets.
- Other folders are for Kotlin code that will be compiled for only the platform indicated in the folder name. For example, if you want to use Apple’s CoreCrypto for the iOS part of your Kotlin app, the iosMain folder would be the right place for such calls. Similarly, if you want to edit the Desktop (JVM) specific part, the jvmMain folder is the appropriate location.
-
/iosApp contains iOS applications. Even if you’re sharing your UI with Compose Multiplatform, you need this entry point for your iOS app. This is also where you should add SwiftUI code for your project.
Build and Run Android Application
To build and run the development version of the Android app, use the run configuration from the run widget in your IDE’s toolbar or build it directly from the terminal:
- on macOS/Linux
./gradlew :composeApp:assembleDebug - on Windows
.\gradlew.bat :composeApp:assembleDebug
Build and Run Desktop (JVM) Application
To build and run the development version of the desktop app, use the run configuration from the run widget in your IDE’s toolbar or run it directly from the terminal:
- on macOS/Linux
./gradlew :composeApp:run - on Windows
.\gradlew.bat :composeApp:run
Build and Run Web Application
To build and run the development version of the web app, use the run configuration from the run widget in your IDE's toolbar or run it directly from the terminal:
- for the Wasm target (faster, modern browsers):
- on macOS/Linux
./gradlew :composeApp:wasmJsBrowserDevelopmentRun - on Windows
.\gradlew.bat :composeApp:wasmJsBrowserDevelopmentRun
- on macOS/Linux
- for the JS target (slower, supports older browsers):
- on macOS/Linux
./gradlew :composeApp:jsBrowserDevelopmentRun - on Windows
.\gradlew.bat :composeApp:jsBrowserDevelopmentRun
- on macOS/Linux
Build and Run iOS Application
To build and run the development version of the iOS app, use the run configuration from the run widget in your IDE’s toolbar or open the /iosApp directory in Xcode and run it from there.
Learn more about Kotlin Multiplatform, Compose Multiplatform, Kotlin/Wasm…
We would appreciate your feedback on Compose/Web and Kotlin/Wasm in the public Slack channel #compose-web. If you face any issues, please report them on YouTrack.