Hikotest on Android

The SDK is distributed through JitPack. Add it to your dependency repositories:

dependencyResolutionManagement {
    repositories {
        google()
        mavenCentral()
        maven { url = uri("https://jitpack.io") }
    }
}

dependencyResolutionManagement {
    repositories {
        google()
        mavenCentral()
        maven { url 'https://jitpack.io' }
    }
}

In the panel, open your project and go to Settings → SDK Integration. You'll see two values with copy buttons:

Create an Application subclass, configure the SDK once with your two values and kick off initialization. The SDK downloads (or loads the cached) release.wasm from the panel and starts its background update loop.

class AppDelegate : Application() {

    private val appScope = CoroutineScope(SupervisorJob() + Dispatchers.IO)

    override fun onCreate() {
        super.onCreate()

        Hikotest.configure(
            HikotestConfig.Builder()
                .panelBaseUrl("https://your-panel.hikotest.app") // from Settings → SDK Integration
                .projectId("your-project-id")                    // from Settings → SDK Integration
                .build()
        )

        appScope.launch {
            runCatching { Hikotest.initialize(this@AppDelegate) }
        }
    }

    override fun onTerminate() {
        super.onTerminate()
        Hikotest.shutdown()
        appScope.cancel()
    }
}

Register it in the manifest:

<application
    android:name=".AppDelegate"
    ... >

The SDK exposes a StateFlow you can collect from a Composable, ViewModel or Activity:

val initState by Hikotest.initState.collectAsState()

when (initState) {
    is HikotestInitState.Idle,
    is HikotestInitState.Loading -> { /* show loading indicator */ }
    is HikotestInitState.Ready   -> { /* SDK ready, enable UI */ }
    is HikotestInitState.Error   -> { /* show error message */ }
}

The recommended path is the generated Kotlin wrapper. Every deploy writes sdk/kotlin/HikotestFunctions.ktinto your project's release — parameter names, types and doc comments included. Copy it into your app and get compile-time-safe calls over OTA logic:

// Signatures and docs come from your panel deploy
val price = HikotestFunctions.applyCampaign(1000.0, "VIP30")

You can also call dynamically with a signature token — int, float, string and boolean are supported, with up to five named parameters per function:

val result = Hikotest.execute(
    "applyCampaign",
    "(float,string)->float",
    1000.0, "VIP30"
)

Some functions (payments, pricing, authorization) should never change over-the-air. Download a release you trust from the panel (release.wasm + manifest.json), ship it in your app's assets/ and pass it at configure time:

Hikotest.configure(
    HikotestConfig.Builder()
        .panelBaseUrl("https://your-panel.hikotest.app")
        .projectId("your-project-id")
        .localBundle(
            assets.open("release.wasm").readBytes(),
            assets.open("manifest.json").bufferedReader().readText(),
        )
        .lockedFunctions("applyPayment") // device-side lock list (optional)
        .build()
)

• A function runs from the embedded local bundle when the live manifest marks it ota:false (locked in the panel) or it is in your lockedFunctions list. Everything else keeps hot-reloading from the live OTA bundle.
• The device wins. The union is one-way: even if the panel unlocks a function remotely, anything in lockedFunctions keeps running from the embedded bundle until you ship an app update.
• A locked function missing from the embedded bundle raises a clear error — there is no silent OTA fallback.
• Fully offline mode: configure only localBundle (no panel, no repo) and call Hikotest.initialize() — no context needed, the SDK never touches the network.
• Hikotest.isLocallyPinned(name) tells you where calls are served from.

• Every deploy (and rollback) from the panel publishes an immutable release with a bumped bundle version (e.g. v1.0.7).
• The SDK periodically asks the panel for the latest version in the background; when a new one appears, the bundle is downloaded, cached and hot-loaded — no app restart, no store release.
• The last downloaded bundle is cached locally, so the app starts offline with the most recent logic.
• Wrapper code only changes when a function signature changes; internal logic updates arrive without touching your codebase.

• 404 / "project not found": re-copy panelBaseUrl and projectId from Settings → SDK Integration — a wrong Project ID is the usual cause. Make sure the project has at least one deployed function.
• "Missing export" errors on string functions: the bundle predates the current string ABI — redeploy the project from the panel to regenerate it.
• Stuck in Loading: initialization needs network on the first run; afterwards the cached bundle is used.