voussoir

Android and iOS

Both mobile platforms reuse the command contract, registry, allowlist and security policy. What differs is the transport and who owns the event loop, and therefore which voussoir commands apply.

Android

voussoir android build            # APK for arm64-v8a
voussoir android build --aab      # signed App Bundle for Play
voussoir android build --abi x86_64 --api 30
voussoir android run              # install and launch on a device or emulator

voussoir init scaffolds android/ as a Gradle project, so nothing is generated at build time except the Kotlin that wry writes (which is git-ignored).

The platform is different enough that it lives in its own crate, voussoir-android:

The envelope, allowlist and policy are shared through a transport seam, so a command does not know which platform it is on. The instrumentation suite runs on an emulator in CI, then launches the app with no instrumentation attached and fails on a FATAL EXCEPTION or an UnsatisfiedLinkError.

iOS

voussoir ios build                # simulator app
voussoir ios build --target device
voussoir ios run                  # install and launch on a booted simulator
voussoir ios verify               # build, install, launch, assert the Rust entry is reached

iOS keeps the custom-scheme transport: WKURLSchemeHandler intercepts voussoir://localhost exactly as the desktop does, so the origin and the security policy are the desktop ones. This is deliberate and is the one mobile platform where the http:// workaround is not needed.

Two differences matter in practice:

What is shared

ConcernDesktopAndroidiOS
IPC transportcustom protocolpostMessage bridgecustom scheme
Envelope / errorssamesamesame
Allowlistsamesamesame
CSP / navigation policysamesamesame
Command tablestatic (or hot in dev)staticstatic
Hot reloadyesnono

Next

Edit this page on GitHub