Valence documentation
Keep the native core, swap the web shell. Your web app becomes your mobile app’s interface, ships safely and works offline.
Valence is an open-source architecture. A small Flutter host goes through store review and rarely changes. Everything the user sees is your web build, shipped as a signed bundle that each phone verifies, tries and rolls back on its own. Data lives in native SQLite and syncs by sequence number.
Start here
Section titled “Start here”Quick startRun npm create valence@latest in your project and ship the first bundle.
How Valence worksThe host, the bundle, the seed and the sync, and which one carries which kind of change.
Guides
Section titled “Guides”Web appCall native features from your web code, and run the same build as a website.
Typed bridgeDefine methods once in a schema and generate the Dart and TypeScript sides.
Flutter hostWhat the generated host does, and the platform setup it needs.
Data and syncThe seed database, incremental pull, local-first writes and schema versions.
ReleasingSign a bundle, upload it, ramp the rollout and roll back.
Store policyWhat Apple and Google allow, and which rules the tooling checks for you.
Reference
Section titled “Reference”CLIEvery command and flag of the valence CLI and the create-valence wizard.
Configurationvalence.config.json, keyring.json, baseline.json and the project layout.
Bundle formatThe OTA host layout, the pointer, the signed manifest and the check order.
Update protocolThe host update algorithm and the trial, commit and rollback state machine.
Bridge protocolMessages, replies, events, error codes and the nonce.
TroubleshootingError messages from the CLI and the host, with the cause and the fix.