Get Started
Everything you need to run Hikotest end to end — install the SDK, connect it to your project's bundle and make your first over-the-air function call.
How the pieces fit
One fixed SDK per platform
You install the same Hikotest SDK as everyone else — once. There is no project-specific package to maintain or re-publish.
Project content is delivered OTA
Every deploy from the panel publishes an immutable, semver-tagged release (release.wasm + manifest.json) to your project’s build repository. The SDK pulls it over the air.
Typed wrappers are generated
Each deploy also generates Kotlin, Swift and TypeScript wrappers with parameter names and doc comments. Drop them into your codebase for compile-time-safe calls.
Connect with your Project ID — no token
The recommended path needs no GitHub token at all. You give the SDK two values from your project’s Settings → SDK Integration: the panel address and your Project ID. The panel serves updates from its own edge cache, so no credential ever ships inside your app.
- an invited Hikotest account;
- a project in the panel with at least one deployed function;
- your panel address and Project ID— both are shown, ready to copy, under your project's Settings → SDK Integration. That's it: no GitHub token, no repository names.
(Prefer the older token-based setup, or already using it? Every platform guide keeps a Connect via GitHub token (legacy) section.)
Pick your platform
Android
Kotlin · Gradle (Groovy & KTS) · JitPack · Chicory runtime
Open guideiOS
Swift · Swift Package Manager · WasmKit runtime
Open guideWeb
TypeScript / JavaScript · npm · Node 18+ and modern browsers
Open guideStandalone
No SDK, no network — ship release.wasm inside your app and call it with a drop-in loader
Open guide