<!-- Stacklift documentation: "Stack adapters". Source: https://stacklift.joynul.com/docs/adapters · All pages for LLMs: https://stacklift.joynul.com/llms-full.txt -->

> About Stacklift: Stacklift is a hosted platform with source-available SDKs for shipping app releases and over-the-air updates. It works for mobile (React Native, Expo, Flutter, native iOS and Android, Kotlin Multiplatform, .NET MAUI, Unity), web, desktop (Electron, .NET, Java) and backend apps. Developers create releases with the `stacklift` CLI or the dashboard; the server verifies and signs every artifact (SHA-256 + Ed25519), deploys releases to channels with staged rollouts and rollback, and app SDKs check, download and verify updates. Native apps can change screens over the air with server-driven UI layouts and logic with sandboxed scripts, within App Store and Google Play rules. Apps never depend on Stacklift to keep working: everything has a built-in fallback and an exit path.
>
> This page: What each stack can and cannot update, with the full capability matrix.

# Stack adapters

Stacklift does not assume every stack can be updated the same way. Each ecosystem is an **adapter** that declares what is technically and contractually possible, and the control plane enforces it.

An adapter describes:

- **Capabilities** — for each update mechanism (`ota`, `web-deploy`, `backend-deploy`, `native-release`, `desktop-update`, `config-assets`): a support level (`supported`, `partial`, `planned`, `unsupported`), platforms, whether clients verify signatures, platform **restrictions** and Stacklift's own **limitations**.
- **Artifacts** — accepted kinds, file extensions, size caps and platforms.
- **Rollbackable kinds** — which artifact kinds can be reverted by repointing a channel. Native binaries and desktop installers never can.
- **Detection** — how `stacklift init` recognises the stack from a file listing.
- **Validation** — project configuration and artifact checks (`validateProjectConfig`, `validateArtifact`).
- **Integration guide** — Markdown shown in the dashboard and docs.
- **Client runtime** — whether anything exists on the device side to *apply* updates.

```ts
interface StackAdapter {
  id: string; displayName: string; language: string;
  ecosystem: 'mobile' | 'desktop' | 'web' | 'backend';
  maturity: 'beta' | 'alpha' | 'planned';
  clientRuntime: { status: 'available' | 'partial' | 'planned' | 'not-applicable'; notes: string };
  platforms: Platform[];
  capabilities: AdapterCapability[];
  artifacts: ArtifactSpec[];
  rollbackableKinds: ArtifactKind[];
  detect(probe: FileProbe): DetectionResult;
  validateProjectConfig(config): ValidationIssue[];
  validateArtifact(input): ValidationIssue[];
  integrationGuide(): string;
}
```

Register a new adapter with `registry.register(adapter)` from `@stacklift/adapters`. Everything else — the API, CLI validation, dashboard capability panel and this page — reads from the registry.

## Capability matrix

Generated from the registry by `pnpm docs:adapters` (CI fails if it is stale).

<!-- adapters:start (generated by scripts/adapters-docs.mjs — do not edit) -->

Legend: **supported** = implemented end to end; *partial* = usable with the restrictions listed in the adapter; *planned* = designed, **not implemented**; *never* = technically or contractually impossible and never offered; *n/a* = not a capability of this stack.

### Mobile (and cross-platform)

| Stack | Maturity | Platforms | OTA | Server UI | Scripts | Native release | Desktop installer | Config & assets |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| `flutter` Flutter | planned | android, ios, web, windows, macos, linux | planned | partial | partial | partial | partial | partial |
| `react-native` React Native | alpha | android, ios | partial | partial | n/a | partial | n/a | partial |
| `expo` Expo | alpha | android, ios | partial | n/a | n/a | partial | n/a | partial |
| `android` Android (Kotlin) | alpha | android | never | partial | partial | partial | n/a | partial |
| `ios` iOS (Swift) | alpha | ios | never | partial | partial | partial | n/a | partial |
| `kmp` Kotlin Multiplatform / Compose Multiplatform | alpha | android, ios, windows, macos, linux | never | partial | partial | partial | partial | partial |
| `capacitor` Capacitor / Ionic | alpha | android, ios, web | partial | n/a | n/a | partial | n/a | partial |
| `nativescript` NativeScript | alpha | android, ios | partial | n/a | n/a | partial | n/a | partial |
| `maui` .NET MAUI | alpha | android, ios, windows, macos | never | partial | partial | partial | partial | partial |
| `unity` Unity | alpha | android, ios, windows, macos, linux | never | partial | partial | partial | partial | partial |

**Client runtime** (what exists on the device to apply updates):

- **Flutter** — *partial*. The Dart SDK (packages/sdk-dart) checks, downloads and verifies config/asset bundles, web builds and desktop installers, and with packages/sdk-flutter-scripts runs signed script bundles (scripted logic updates). Dart code OTA on Android/iOS ("code push") needs a patched Flutter engine and a patch toolchain Stacklift does NOT ship.
- **React Native** — *partial*. @stacklift/react-native (packages/sdk-react-native) loads a new JS bundle on the next launch, confirms it, and rolls back to the last good or built-in bundle when a launch never confirms or crashes first. Its native side is the Swift SDK (iOS) and the Android SDK, which verify every bundle (SHA-256 + Ed25519). It also renders server-driven screens. Verified on the iOS simulator, an Android emulator and a physical Android 16 phone; not published to npm yet.
- **Expo** — *partial*. @stacklift/sdk-js performs check → download → verification in JS. Activating the bundle needs a native loader or an implementation of the Expo Updates protocol; Stacklift ships neither, so Expo apps do not use expo-updates against Stacklift yet.
- **Android (Kotlin)** — *not-applicable*. Binaries are distributed by the platform store. Remote config/asset bundles can be fetched and verified with the Android SDK (packages/sdk-android: Compose screens, QuickJS scripts, update lifecycle; built on the Java SDK in packages/sdk-java; tested on an Android 17 emulator and a physical Android 16 phone; Ed25519 needs Android API 33+, or register BouncyCastle/Conscrypt).
- **iOS (Swift)** — *not-applicable*. Binaries are distributed by the platform store. Remote config/asset bundles can be fetched and verified with the Swift package (packages/sdk-swift, tested with swift test on macOS).
- **Kotlin Multiplatform / Compose Multiplatform** — *partial*. On Android and JVM desktop use the Java SDK (packages/sdk-java, tested on JDK 21). packages/sdk-kotlin is a coroutine wrapper over it for androidMain/jvmMain; it has NOT been compiled or tested (no Kotlin toolchain in Stacklift CI yet). There is no Kotlin iOS implementation: call the Swift package (packages/sdk-swift) from iOS code.
- **Capacitor / Ionic** — *partial*. @stacklift/sdk-js checks, downloads and verifies the web bundle. Unpacking it and pointing the WebView at it needs a native Capacitor plugin that Stacklift does not ship yet.
- **NativeScript** — *partial*. @stacklift/sdk-js checks, downloads and verifies the bundle. Activating it on-device is not implemented.
- **.NET MAUI** — *partial*. Stacklift.Sdk (netstandard2.0, tested on .NET 10) checks, downloads and verifies. MAUI platform projects were not built here.
- **Unity** — *partial*. Stacklift.Sdk (netstandard2.0) can be used from Unity for check, download and verification; it needs the BouncyCastle assembly. Not run inside Unity here. Stacklift does not implement the Addressables remote-catalog protocol.

### Desktop

| Stack | Maturity | Platforms | Desktop installer | Native release | OTA | Config & assets |
| --- | --- | --- | --- | --- | --- | --- |
| `electron` Electron | alpha | windows, macos, linux | partial | partial | planned | partial |
| `tauri` Tauri | planned | windows, macos, linux | partial | partial | planned | partial |
| `dotnet-desktop` .NET desktop (WPF / WinForms / WinUI) | alpha | windows | partial | partial | never | partial |
| `macos` macOS (Swift / AppKit) | alpha | macos | partial | partial | never | partial |
| `jvm-desktop` JVM desktop (JavaFX / Compose / Swing) | alpha | windows, macos, linux | partial | partial | never | partial |
| `qt` Qt / C++ | alpha | windows, macos, linux | partial | partial | never | partial |
| `native-desktop` Other native desktop | alpha | windows, macos, linux | partial | partial | never | partial |

**Client runtime** (what exists on the device to apply updates):

- **Electron** — *partial*. @stacklift/sdk-electron checks, downloads and verifies the installer in the main process and hands it to the OS. It is unit-tested with fakes for the Electron APIs, not inside a running Electron app. No in-place asar patching.
- **Tauri** — *planned*. A Rust plugin is provided as source in packages/sdk-tauri. It has NOT been compiled or tested (no Rust toolchain in Stacklift CI yet). From the web frontend you can use @stacklift/sdk-js for check and verification.
- **.NET desktop (WPF / WinForms / WinUI)** — *partial*. Stacklift.Sdk (netstandard2.0, tested on .NET 10) checks, downloads and verifies. Launching the MSI/MSIX/EXE is done by your app.
- **macOS (Swift / AppKit)** — *partial*. The Stacklift Swift package (CryptoKit, tested with swift test on macOS) checks, downloads and verifies. Opening the DMG/PKG is done by your app. Sparkle can still be used for the install step.
- **JVM desktop (JavaFX / Compose / Swing)** — *partial*. The Java SDK (JDK 17+, no dependencies, tested on JDK 21) checks, downloads and verifies. Running the installer is done by your app.
- **Qt / C++** — *planned*. No C++ SDK is shipped. The delivery API is plain HTTPS + JSON and the signature is Ed25519 over a documented text payload, so any language can verify it (see docs/sdk.md).
- **Other native desktop** — *planned*. Choose this for any toolkit without its own adapter (GTK, wxWidgets, Win32, Go, Rust ...). No client SDK is shipped for it; the HTTP API and signature format are documented in docs/sdk.md.

### Web

| Stack | Maturity | Platforms | Web deploy | Config & assets |
| --- | --- | --- | --- | --- |
| `react` React (SPA) | beta | web | **supported** | **supported** |
| `nextjs` Next.js | alpha | web | **supported** | **supported** |
| `vue` Vue | alpha | web | **supported** | **supported** |
| `nuxt` Nuxt | alpha | web | **supported** | **supported** |
| `angular` Angular | alpha | web | **supported** | **supported** |
| `svelte` Svelte | alpha | web | **supported** | **supported** |
| `sveltekit` SvelteKit | alpha | web | **supported** | **supported** |

**Client runtime** (what exists on the device to apply updates):

- **React (SPA)** — *partial*. Stacklift versions, signs and serves the build. Serving it to users is up to your host/edge/CDN: fetch the verified artifact in your deploy pipeline with the delivery API (docs/sdk.md) or @stacklift/sdk-core (Node) / @stacklift/sdk-js. No hosting is provided.
- **Next.js** — *partial*. Stacklift versions, signs and serves the build. Serving it to users is up to your host/edge/CDN: fetch the verified artifact in your deploy pipeline with the delivery API (docs/sdk.md) or @stacklift/sdk-core (Node) / @stacklift/sdk-js. No hosting is provided.
- **Vue** — *partial*. Stacklift versions, signs and serves the build. Serving it to users is up to your host/edge/CDN: fetch the verified artifact in your deploy pipeline with the delivery API (docs/sdk.md) or @stacklift/sdk-core (Node) / @stacklift/sdk-js. No hosting is provided.
- **Nuxt** — *partial*. Stacklift versions, signs and serves the build. Serving it to users is up to your host/edge/CDN: fetch the verified artifact in your deploy pipeline with the delivery API (docs/sdk.md) or @stacklift/sdk-core (Node) / @stacklift/sdk-js. No hosting is provided.
- **Angular** — *partial*. Stacklift versions, signs and serves the build. Serving it to users is up to your host/edge/CDN: fetch the verified artifact in your deploy pipeline with the delivery API (docs/sdk.md) or @stacklift/sdk-core (Node) / @stacklift/sdk-js. No hosting is provided.
- **Svelte** — *partial*. Stacklift versions, signs and serves the build. Serving it to users is up to your host/edge/CDN: fetch the verified artifact in your deploy pipeline with the delivery API (docs/sdk.md) or @stacklift/sdk-core (Node) / @stacklift/sdk-js. No hosting is provided.
- **SvelteKit** — *partial*. Stacklift versions, signs and serves the build. Serving it to users is up to your host/edge/CDN: fetch the verified artifact in your deploy pipeline with the delivery API (docs/sdk.md) or @stacklift/sdk-core (Node) / @stacklift/sdk-js. No hosting is provided.

### Backend

| Stack | Maturity | Platforms | Backend deploy | Config & assets |
| --- | --- | --- | --- | --- |
| `node` Node.js | alpha | server | partial | **supported** |
| `python` Python | alpha | server | partial | **supported** |
| `go` Go | alpha | server | partial | **supported** |
| `java` Java / JVM | alpha | server | partial | **supported** |
| `dotnet` .NET | alpha | server | partial | **supported** |

**Client runtime** (what exists on the device to apply updates):

- **Node.js** — *partial*. Stacklift stores signed server bundles or container image references and tracks which release each channel points to. Your CD system (fetching and verifying the artifact through the delivery API or an SDK) performs the actual rollout to servers/orchestrators — Stacklift does not run your infrastructure.
- **Python** — *partial*. Stacklift stores signed server bundles or container image references and tracks which release each channel points to. Your CD system (fetching and verifying the artifact through the delivery API or an SDK) performs the actual rollout to servers/orchestrators — Stacklift does not run your infrastructure.
- **Go** — *partial*. Stacklift stores signed server bundles or container image references and tracks which release each channel points to. Your CD system (fetching and verifying the artifact through the delivery API or an SDK) performs the actual rollout to servers/orchestrators — Stacklift does not run your infrastructure.
- **Java / JVM** — *partial*. Stacklift stores signed server bundles or container image references and tracks which release each channel points to. Your CD system (fetching and verifying the artifact through the delivery API or an SDK) performs the actual rollout to servers/orchestrators — Stacklift does not run your infrastructure.
- **.NET** — *partial*. Stacklift stores signed server bundles or container image references and tracks which release each channel points to. Your CD system (fetching and verifying the artifact through the delivery API or an SDK) performs the actual rollout to servers/orchestrators — Stacklift does not run your infrastructure.

<!-- adapters:end -->

## Honest limits

- **Native iOS/Android** binaries can only ship through the stores. Stacklift tracks them; it cannot update them.
- **iOS** (App Store Review Guideline 3.3.2) and **Android** (Google Play policy) restrict downloaded code to interpreted code that doesn't change the app's primary purpose. Compliance is the developer's responsibility.
- **Desktop** apps update by installing a new signed build (`desktop-installer`). Stacklift delivers and verifies it; your app runs it. OS code signing/notarization is yours, installers can't be rolled back, there are no delta updates, and store builds must update through their store. See [Desktop apps](https://stacklift.joynul.com/docs/desktop.md).
- **Expo, Capacitor, NativeScript** can change their JS/web layer over the air within store rules; the on-device loader that applies it is **not shipped** (partial).
- **Kotlin Multiplatform and Tauri** SDKs are untested source (no Kotlin/Rust toolchain in CI). See [SDKs](https://stacklift.joynul.com/docs/sdk.md).
- **Flutter** Dart OTA is **planned**: it needs a patched engine and a patch toolchain Stacklift doesn't ship.
- **React Native** JS-bundle OTA is **partial**: control plane, signing, rollout and delivery work; the on-device bundle loader isn't shipped yet.
- **Web and backend** stacks use deployments: Stacklift versions, signs and serves artifacts, and repoints a channel. Hosting is yours.
