llms.txt
+126 −8
− > Shipvo is an open-source React Native framework: build once, publish for people and AI agents. Phones get signed over-the-air updates; AI agents open the same release in a simulated phone they can see and operate over MCP; parity between the two is measured and published.− - Developers test their app in CI with @shipvo/test (typed tests, Vitest or any runner) against the headless simulator on a plain Linux runner: no emulator or device. It catches logic and flow bugs, not native crashes or slow-phone performance.− - AI agents do not yet buy things for real people through Shipvo apps. That needs consent, spend limits and a checkout contract, and is on the roadmap.− - Packages are on npm under @shipvo (cli, mcp, runtime, device, sim, schema). Source: https://github.com/shipvo/shipvo− ## Learn− - [Videos](https://shipvo.dev/docs/videos.md): Short captioned videos that show how Shipvo works: over-the-air updates, signing, staged rollout and rollback, in plain words.− - [Simulator vs device parity](https://shipvo.dev/docs/parity-results.md): Simulator vs device parity: every screen of three purchase flows compared on Android and iOS, with every known gap listed, not hidden.− - [Shipvo vs Expo](https://shipvo.dev/compare/): side-by-side comparison, including where Expo is the better choice+ > Shipvo is the mobile platform for the AI era: your agent builds the app, tests it on a phone in your browser, records the demo, and ships it to the stores and to every phone. Shipvo is open source (Apache-2.0).+ ## For AI coding agents+ Install (only what exists today):+ ```+ npx skills add shipvo/shipvo --skill shipvo -g # installs the Shipvo skill: exact commands for your agent+ curl -fsSL https://shipvo.dev/install.sh | bash (macOS, Linux, WSL)+ irm https://shipvo.dev/install.ps1 | iex (Windows PowerShell)+ npx -y @shipvo/cli agents setup+ ```+ MCP server (runs on your machine, stdio):+ ```json+ { "mcpServers": { "shipvo": { "command": "npx", "args": ["-y", "@shipvo/mcp"] } } }+ ```+ Hosted simulator: https://sim.shipvo.dev/mcp (header `Authorization: Bearer <key>`; clients that cannot send headers use https://sim.shipvo.dev/mcp/<key>). Get a key with `npx -y @shipvo/cli login`. It signs in with GitHub in a browser (device flow), so there is no browser-free way to get a key yet. `shipvo mcp` prints the config for Claude, Cursor and ChatGPT.+ - [All docs in one file](https://shipvo.dev/llms-full.txt)+ - [Docs index](https://shipvo.dev/docs.md)+ - [Agents and Shipvo apps](https://shipvo.dev/docs/agents.md)+ ## How Shipvo works+ 1. Run the app on Shipvo Phone, a phone frame in your browser. No emulator, no Xcode. Command: `shipvo run android` (or `ios`). [Docs](https://shipvo.dev/docs/run.md)+ 2. Test it on that phone: taps, gestures, offline, permissions. Command: `shipvo test`, or drive it over MCP. [Docs](https://shipvo.dev/docs/testing.md)+ 3. Record a demo video of the app in the phone frame, with the MCP tools record_start and record_stop. [Docs](https://shipvo.dev/docs/record.md)+ 4. Get to the stores: store forms, screenshots and testers. Command: `shipvo store setup`. EAS or your own CI builds the native binary. [Docs](https://shipvo.dev/docs/store.md)+ 5. Ship every later change as a signed over-the-air update with staged rollout and rollback. Commands: `shipvo publish`, `shipvo rollback`. [Docs](https://shipvo.dev/docs/getting-started.md)+ 6. Check the measured parity of the simulator against the Android emulator and iOS Simulator. [Results](https://shipvo.dev/docs/parity-results.md)+ ## Straight answers+ **Do I need a phone or an emulator?** No. `shipvo run` opens a phone frame in your browser, and tests run on a plain Linux runner. Use an emulator or device only if you want to check native behaviour.+ **Does it replace Expo or EAS?** No. EAS or your own CI still builds the native binary. Shipvo adds the browser phone, agent testing, recording, store steps and signed updates. See [Shipvo vs Expo](https://shipvo.dev/compare/).+ **Is it free?** The hosted services (api.shipvo.dev and sim.shipvo.dev) are free during the beta. The code is free.+ **Can it be self-hosted?** Yes, on Cloudflare. [Docs](https://shipvo.dev/docs/self-hosting.md)+ **Which frameworks?** Expo, bare React Native and Capacitor, as shipped. [Docs](https://shipvo.dev/docs/capacitor.md)+ **How close is the simulator to native?** Every screen is compared with the Android emulator and the iOS Simulator: the 13 screens of the purchase flows are at 100% actionable parity, with the same elements, roles and labels. [Results](https://shipvo.dev/docs/parity-results.md)+ **Where does my data go?** Updates and release data go to the control plane you use: api.shipvo.dev, or your own Cloudflare account if you self-host. You can export release data to your own R2 bucket. [Docs](https://shipvo.dev/docs/telemetry-export.md) and [Privacy](https://shipvo.dev/privacy/)+ **Is it open source?** Yes, Apache-2.0: https://github.com/shipvo/shipvo+ - Developers test their app in CI with @shipvo/test (typed tests, Vitest or any runner) against the headless simulator on a plain Linux runner, or on a real Android emulator or iOS Simulator with --device agent-device. It catches logic and flow bugs.+ - Real orders go through the app's own checkout to the control plane, start as unverified, and the owner settles them after checking the payment (docs: taking-real-orders).+ - CLI commands include init, sim, preview, publish (with --dry-run and --dry-run-policy), rollback, auto-halt, audit, run (android or ios, a phone frame in your browser), promote (with --report), test (with --repair, --report and --report-md), explore, lumi, eval (run, report), agents setup (with --hosted), sim (with --hosted), store (details, setup, screenshots, testers), doctor, eas setup and ci init (Expo and Capacitor).+ - MCP tools include open_app (attaches to a live shipvo run phone; takes room so phones share one backend), upload_build (test your own build on the hosted phone), screen, tap, type, scroll, back, screenshot, wait_for, and record_start, record_marker, record_stop for MP4 demo videos.+ - Release rules live in a policy section of shipvo.json (maxBand, agentMaxBand, blocked weekdays) and the control plane keeps an audit log of publishes, halts and rollbacks.+ - Packages are on npm under @shipvo (capacitor, cli, device, mcp, mcp-tools, runtime, schema, sim, spec, store, test). Source: https://github.com/shipvo/shipvo+ - [Playground: try Shipvo in your browser](https://shipvo.dev/docs/playground.md): Try a sample app on an Android phone and an iPhone in your browser, with device features, signed updates and rollback, and a shareable many-phones link.
Showing the first 40 of each.