This is the Kotlin Multiplatform manager for Reseam: one Compose codebase for Android and desktop.

composeApp/src/commonMain/kotlin/app/reseam/manager/data      bundles, patched apps, settings, trust
composeApp/src/commonMain/kotlin/app/reseam/manager/sdk       wire models and the calls into the Reseam SDK
composeApp/src/commonMain/kotlin/app/reseam/manager/ui        Compose UI, theme, routing, and viewmodels
composeApp/src/commonMain/kotlin/app/reseam/manager/platform  platform contracts (HTTP, installed apps, app presentation, installing)
composeApp/src/jvmCommonMain                                  implementations shared by Android and desktop
composeApp/src/androidMain                                    Android application and platform adapters
composeApp/src/jvmMain                                        desktop entry point and platform adapters

Mental Model

1. App.kt owns the app shell and route table. AppGraph builds the repositories every screen shares.
2. Viewmodels own UI state transitions. They should not render UI and should expose one obvious path for each user action.
3. Repositories in data/ persist state as JSON files and decide what is trusted: the official bundle is pinned to Reseam's signing key, anything else is confirmed by the user once per signer.
4. Platform adapters do HTTP, file picking, app presentation, and installation. Android and desktop differences stay there.

A picked file is identified by the SDK, not its file name: the engine reads the label and icon from the archive's resources, Android's package manager localizes and renders them, and desktop composites adaptive icons itself. The icon is kept as a file so the patch flow and the library can show it.

Patch creation is a three-step flow: Pick app -> Patches -> Run.

Reseam SDK

The engine comes in as one Maven dependency, app.reseam:reseam-sdk, pinned in gradle/libs.versions.toml to the engine version it was built against. Android gets libreseam_sdk.so for every ABI; desktop gets the same engine as a JVM resource and runs it inside the app's own JVM.

Manager requests automatic output for APK, APKM, and XAPK inputs. The SDK resolves the component set and returns the concrete artifact in PatchOutcome.output; Manager saves and installs that artifact without inferring its layout from the input filename or inspection state. Changes to this JSON contract require rebuilding the native SDK together with Manager, even when the generated Kotlin bindings are unchanged.

To build the SDK from a local engine checkout, from ../reseam:

cargo xtask regen sdk
cargo xtask jni-host
./gradlew publishToMavenLocal -PreseamSdkVersion=0.5.1

Build and Run Android Application

./gradlew :composeApp:assembleDebug

Build and Run Desktop (JVM) Application

./gradlew :composeApp:run

Tests

./gradlew :composeApp:jvmTest

Release

The app version is managerVersion in gradle.properties. Tag vX.Y.Z to release: CI builds the APKs and desktop packages, writes manager.json, and uploads everything to the Forgejo release. Installed apps check that index on launch and offer the download.