Skip to content
Patch Docs

Patch documentation

Patch ships over-the-air code updates to native Swift iOS apps. You write ordinary Swift; the build engine works out which parts can run as WebAssembly, compiles those, and ships them as a small module that runs on-device in WasmKit. Your signed App Store binary never changes — only the interpreted layer updates.

Terminal window
brew install patch-release/tap/patchcli
cd MyApp && patchcli init
Quick StartInstall the CLI and ship your first patch in about ten minutes.
How it worksThe Swift→WebAssembly pipeline and the on-device runtime.
What it can & can't updateMeasured coverage, and the limits that are permanent.
The fingerprintWhy a patch stops applying after you change native code.

If you’ve used CodePush or Expo

Section titled “If you’ve used CodePush or Expo”

Patch is the equivalent for native Swift and SwiftUI — no JavaScript bridge, no web views, no cross-platform runtime. CodePush and Expo/EAS Update patch a JavaScript bundle; Shorebird patches Dart. None of them touch native Swift. The side-by-side table is on How Patch compares, and the marketing site covers each one individually: vs CodePush, vs EAS Update, vs Shorebird.

Open source

Section titled “Open source”
The packagesThe SDK (MIT) and the engine (Apache-2.0) — both in patch-swift, what's in each, and how to build from source.
Running it yourselfReference architectures for GCP, AWS and Azure, and what static hosting can't do.
Section titled “Related”