HealkiteDocs

Quick start

Ship your first over-the-air update in about ten minutes.

1. Create an app and a channel

Sign in at app.healkite.com with GitHub, create an app and copy the channel key from Settings. Or from the terminal, with an access key from API & MCP:

sh
npx healkite login --api-url https://api.healkite.com --token hk_…
npx healkite apps create "My App"
npx healkite channels create production --app app_…        # prints the channel key
sh
npx healkite keys generate                                  # writes healkite-signing.pem, prints the public key
npx healkite apps set-key --app app_… --from-private healkite-signing.pem

Keep healkite-signing.pem out of git and store it as a CI secret. Once a key is set, the API and your app refuse unsigned releases.

3. Add the SDK

sh
npm install @healkite/react-native && cd ios && pod install

Set the CDN URL, channel key and keys in Info.plist / strings.xml, load the OTA bundle in release builds and call Healkite.sync() after your first screen. Full steps: React Native SDK, or Expo for a config plugin with no native edits.

4. Ship a store build

Build and publish your app as usual. That binary's version is its runtime version.

5. Release an update

sh
npx healkite release -p android -c <channel-key> -r 1.0.0 --sign healkite-signing.pem --guarded

The CLI bundles with Metro, compiles Hermes bytecode, makes diffs against your recent releases, signs and uploads. With --guarded the release starts at 1% and widens every 30 minutes while it's healthy.

6. Watch it

sh
npx healkite stats -c <channel-key> -p android

Or open the app in the dashboard: adoption, crash-free sessions, rollbacks and per-device timelines.

Next: put releases in CI with the GitHub Action.