gomtm-swarm

Public Android host app for gomtm, released under the product name gomtm-swarm.

Current source of truth

This repository is the long-term public Android app host for gomtm.

The active architecture is:

• gomtm remains the device runtime kernel / Android AAR producer
• gomtm-android is the repository host for the public Android app gomtm-swarm, including CI, release, and APK distribution
• the Android shell stays thin and delegates runtime behavior into the published AAR
• legacy monorepo apps/android/ is migration material only, not the future app host

What this repo is responsible for

• a thin single-Activity WebView host shell for the public Android app
• starting and stopping the device-side local gomtm runtime through the foreground service
• exposing minimal host activation primitives to the shared gomtm Web UI through a small Android <-> JS bridge
• requesting screen capture permission for the native remote pipeline
• GitHub Actions CI and release automation
• APK publication
• consuming a published, pinned gomtm-swarm-android.aar
• using the committed pin manifest app/libs/gomtm-swarm-android.json as the CI truth surface for the pinned runtime

What this repo is not responsible for

• re-implementing libp2p or swarm logic in Kotlin
• reviving or continuing development in monorepo apps/android/
• consuming an unpinned latest AAR
• pulling reward-automation business logic into the Android node host

Validation policy

• use GitHub Actions as the build / validation path
• use pull requests for functional changes
• do not treat local Android builds as the acceptance path for this phase

Runtime contract

The app consumes a published gomtm-swarm-android.aar and starts the device-side local Go HTTP runtime through the generated Gomtmruntime surface. The Android WebView bridge stays intentionally small and only exposes:

• getHostInfo()
• getRuntimeSurface()
• ensureRuntimeStarted(payloadJson)
• requestScreenCapture()

The product UI lives in the shared /dash/devices Web experience. The Android shell is responsible for loading that entry URL and exposing host primitives, not for keeping a parallel native dashboard.

Inside the Android app, the embedded WebView should behave like a normal browser surface for the gomtmui app: normal web navigation, normal login redirects, and the same shared page tree. The only Android-specific difference is the additional JS bridge exposed by GomtmWebViewBridge.

Release trigger

This repository no longer relies on repository Actions variables to discover the next swarm runtime.

The committed file app/libs/gomtm-swarm-android.json now pins:

• the gomtm swarm AAR version
• the GitHub release asset URL for the AAR asset
• the GitHub release asset URL for the metadata asset
• the expected SHA256

Updating that file on main is the canonical way to refresh the Android host against a newly published gomtm AAR. Every commit pushed to main automatically allocates the next exact semver patch tag in the current public line (v0.4.x), builds the APK, and publishes a GitHub Release from that tag. If multiple main pushes happen close together, each commit retries tag allocation until it gets its own unique patch version, instead of dropping intermediate releases. The Gradle app version metadata is derived from that release tag so the published APK provenance, release page, and in-app version stay aligned.

The canonical stable download surface for installers is GitHub latest, for example:

• release API: https://api.github.com/repos/codeh007/gomtm-android/releases/latest
• direct APK download: https://github.com/codeh007/gomtm-android/releases/latest/download/gomtm-swarm-arm64-v8a-debug.apk

Host shell shape

The current Android shell has been intentionally reduced to:

• one MainActivity
• one WebView host shell in activity_main.xml
• one foreground-service-owned device runtime
• one screen capture permission entry for native remote capabilities
• one minimal Android <-> JS bridge in GomtmWebViewBridge

Current package boundaries:

• com.gomtm.swarm.platform.lifecycle hosts Android lifecycle, foreground service, host install, and runtime bridge components
• com.gomtm.swarm.platform.remote hosts remote-control protocol handling and device capability adapters
• com.gomtm.swarm.platform.python hosts Python runtime installation and probe support
• com.gomtm.swarm.shell hosts local Node runtime setup and probe helpers
• com.gomtm.swarm.web only hosts the WebView bridge surface
• the old catch-all com.gomtm.swarm.swarm package is no longer the canonical source layout

MainActivity now loads the shared BuildConfig.GOMTM_UI_DEVICES_URL Web entry directly. The embedded WebView does not enforce path allowlists or reroute normal gomtmui navigations out to an external browser. If that page cannot load, the only native fallback is a minimal error text surface; the old native runtime dashboard is no longer a product UI.