Skip to content

Every release crosses the same desk.

Build, sign, roll out to a percentage, watch, then widen or roll back. Here is each step and what it checks.

1

Build

Run your usual web build. The bundle is the folder Capacitor already ships, zipped by the CLI or the dashboard.

  • Up to 100 MB zipped, 500 MB unzipped.
  • One bundle per channel and version.
npx native-update bundle create ./dist --version 4.2.1

2

Sign

Sign it with your private key. The server checks the SHA-256 and the RSA-SHA256 signature on upload, and the plugin checks both again on the device.

  • The private key stays with you or your CI secrets.
  • A bundle that doesn’t match is refused.
npx native-update bundle sign ./bundle.zip --key ./keys/private.pem

3

Roll out

Choose who gets it first. Channels keep production, staging and your own groups apart; the percentage decides how many devices are offered the release.

  • Start at 5%, widen when the numbers look right.
  • Pause at any percentage.
npx native-update deploy ./dist --app com.example.app --rollout 5 --wait

4

Watch

The dashboard counts devices on each release and any that failed to start. Analytics show adoption by version and update checks per day.

  • Failed starts pause the rollout.
  • Notifications and email tell you.

Devices on 4.2.1

301

of 1,204 checked in this week · 0 failed starts

5

Widen or roll back

Widen to everyone, or roll back with one click and keep the release for later. A bundle that never confirms its boot reverts by itself after two cold starts.

  • Undo on every reversible action.
  • Rollback is per release, per channel.
npx native-update builds rollout com.example.app 42 --percent 25

Also in every plan

Delta patches

Only the files that changed travel. A delta that can’t apply falls back to the full bundle.

Store-update prompts

When a release needs native code, tell users a store update is ready.

In-app review

The store’s own review prompt, at a moment you choose.

Public API and CLI

nu_pat_ access tokens for CI, scoped to the apps you choose.

Key restrictions

Each API key can be limited to web origins, Android packages and iOS bundle ids.

Assistants with Speak

A release-notes writer and a docs assistant, both listening when you’d rather talk.

Live updates carry web-layer changes; native changes still ship through the store.