Webview Bundle logowebview-bundle

Overview

A remote is the HTTP server your app downloads new bundles from over the air. You publish a packed .wvb to it, mark a version as current, and clients fetch that version without a native app release.

Publish and download

Publishing is a two-step model, both run from the CLI:

  1. Upload stores a packed version on the remote.
  2. Deploy marks which version is current — the one clients receive.

Clients then check for and download the deployed version through the updater. See Over-the-air for the client-side flow, and Remote configuration for the remote block that wires it up.

Run a remote

There are two ways to run a remote.

Use a provider. A provider gives you a server to deploy and an uploader/deployer pair to drop into your config — no HTTP contract to implement.

Local

Serve bundles from disk for development and testing.

AWS

S3 and CloudFront, with optional KMS signing.

Cloudflare

R2 storage behind a Workers handler.

Build your own. Any server that implements the remote HTTP contract works. See the HTTP spec.

Testing

Test web code that calls the bridge without a native host — mock invoke calls and the platform with mockBridge.

Using the CLI

Run a local remote, publish a version, and download it — the whole update loop from the terminal.

On this page

Publish and downloadRun a remote