Kgothatso Ngako 310d3bbbd3 docs: record Phase 5 of the profiles pull, which completes the ten
9bb34004, 88577bb5 and 29027f2b landed as 8edb52ff, 72b9d3d2 and
ba5ef723, all clean -- including the two picks into docs/README.md, where
the driver's UNION rule was armed and did not fire: git placed the fork's
row between the npub and jvm-target rows and its reading-order sentence
after the npub note's, beside the sentence this plan's own commit had
added there.

The ten are landed. Exactness at the tip is the dry run's: 135 residual
files between Mantra and the rewritten fork, CreateProfileViewModel.kt
the only file that left the residual since the base, and no other file's
residual moved. Both compilers clean, jvmTest 864 -> 868, testDebugUnitTest
420, every audit budget met -- the dry run's numbers exactly, as a
deterministic rewrite replayed onto an unchanged base should give.

One review point, read: MultipleProfilesRoundTripJvmTest reaches the
saved default through the app's getGlobalPrefs rather than building a
GlobalPrefs of its own, and says why in a comment, so the per-process
cache trap is written at the place a future test would copy from.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-13 15:56:26 +02:00
2026-09-09 17:04:09 +02:00
2026-03-24 04:47:19 +02:00
2026-03-23 01:41:39 +02:00
2026-03-23 01:41:39 +02:00
2026-03-23 01:41:39 +02:00

This is a Kotlin Multiplatform project targeting Android, iOS, 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 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…

Description
Mantra as a kotlin multiplatform project
https://mantra.press
Readme 13 MiB
Languages
Kotlin 100%