Getting started

Install the CLI

The birdify CLI is how you create apps, cut releases, and push patches. Install it with one command:

$ curl -fsSL https://cli.birdify.dev/install.sh | sh
$ birdify version
birdify v1.0.0 (darwin/arm64)

On Windows PowerShell, run irm https://cli.birdify.dev/install.ps1 | iex instead.

Create or link an app

Point Birdify at your project. Pass the framework you're on; the SDK is wired in and the app is registered on Birdify cloud (or your self-hosted server).

$ birdify flutter create shop_app
✓ SDK wired · linked shop_app (iOS + Android)

Swap flutter for rn to target React Native (Expo or bare). Those are the two stacks shipping today; native iOS and native Android are in development, and you can track them on the roadmap. See Frameworks for the per-stack setup.

Cut a release

A release is the signed baseline your patches diff against; it matches the binary in the store. Cut one before you patch.

$ birdify release
→ building release bundle…
✓ release 1.0.0 registered · signed

Ship a patch

Make a code or UI change, then birdify patch. Birdify diffs against the release, uploads only what changed, and delivers it over the air. It applies on the next launch; no rebuild, no store review.

$ birdify patch
→ diffing + uploading bundle…
✓ patch #1 live · # applies on next launch

Verify & track

Watch the rollout (how many devices received, downloaded, and installed the patch) and roll it back instantly if anything looks off.

$ birdify status
patch #1 · sent 1,240 · downloaded 1,205 · installed 1,190

A bad patch? birdify rollback pulls it fleet-wide, and any patch that fails to boot auto-reverts on device. See Rollback & health checks.

Next steps

• CLI reference; every command and flag: create, release, patch, rollback, status.
• How Birdify works, what actually travels over the air, and why it stays App-Store-safe.
• Signing & verification, how bundles are signed and checked on device.