Peach
Peach is a simulator for iOS and Android apps that runs in its own desktop app or a browser tab. You point it at the dev server you already run, and your app is on a simulated iPhone or Android phone in seconds. There is no virtual machine, no streamed device, and no native build in the inner loop, so it runs on a laptop, a Linux CI runner, or a small cloud box.
Peach is in public beta. React Native is the most complete path today; Swift and Kotlin apps run in an earlier beta.
Pick your section
The docs are split by what you are building. Start in the section that matches your app, and come back here for anything about the simulator itself.
| section | read it if you | start with |
|---|---|---|
| Simulator (you are here) | want to install Peach, set up devices and settings, test, share previews, or wire up an agent | Install, then Quick Start |
| React Native | build with Expo, Metro, or One, for iOS, Android or both | React Native overview |
| iOS | build a Swift app with SwiftUI or UIKit, or write Swift modules for an Expo app | iOS overview |
| Android | build a Kotlin app with Jetpack Compose, or write Kotlin modules for an Expo app | Android overview |
A React Native app that targets both platforms lives in the React Native section. You only need the iOS or Android sections for native code you write in Swift or Kotlin.
What runs today
- +React Native, Expo and One apps. Start your usual dev server and run
peach open 8081. Peach loads the bundle your server already serves, with no per-app install and no native build. Library support is measured and published per package; see Library compatibility. - +Swift apps (beta).
peach openpreviews a SwiftPM package or the app target of an Xcode project or workspace, with live Swift edits. When your app imports a module Peach does not provide, the command lists it with the files that import it, so you see the gap before you debug it. See Running Swift apps. - +Compose apps (beta).
peach openruns an Android app module from its launcher activity. Gradle values must be literals and dependencies must come from the Compose set Peach pins; anything else is rejected with its location. See Running Compose apps. - +iOS and Android devices. Pick an iPhone or Android phone profile with
--device, and switch it on a running sim withpeach device set. The full list is on Devices and settings.
Try it without installing
The peachsim.com home page runs the real simulator. Press play on the demo tour, or tap into the phone yourself. The Bluesky and Uniswap pages each open one real app bundle in the same simulator. Try Peach without a project covers every no-setup path.
Get started
Installation
Install the CLI and engine runtime, and keep them current.
Quick Start
Open your app, run a flow, and share a preview link.
Your First Test
Run a Maestro YAML or Detox test.
Simulating the Device
Permissions, location, camera, appearance, and storage.
Fast path
The installer downloads one standalone peach executable for macOS or Linux.
It needs no Node.js, npm, or Bun on the machine. Then, from your app’s project
root, with its dev server running:
Run peach open from the project root so it can find your custom fonts,
splash screen, and other app configuration.
Built for agents
The same peach CLI a person uses is how an AI coding agent drives the
simulator. There is no separate agent runtime to configure.
- +Screens an agent can read.
peach describelists what is on screen as text, with each element’s type, label and position, andpeach what-happenedreports what just changed. Commands that write settle on their own for a bounded time; usepeach waitfor anything slower. - +Light enough to run many. Each sim is a browser tab’s worth of memory, so several agents, a CI job and a person can share one machine.
peach claimleases a sim to one driver so nobody steals another’s taps.
See Agents setup to get started.
How it works
Peach re-implements the iOS and Android surfaces that apps draw on, using Skia through CanvasKit, the WebAssembly build of the graphics engine behind Chrome and Flutter. Your app’s JavaScript runs in a worker, lays out through Yoga, and paints through Skia on the GPU, the same pipeline shape as native React Native. Native UI state lives in a separate worker, so scrolling and native-driven animations keep moving while your app’s JavaScript is busy. How Peach works tells the full story.
How accurate is it?
We measure it. Peach is checked against real iOS with pixel diffs, library by library and through animations, and the results are public on Proof. How proof works explains the method.
Rebuilding iOS, Android, React Native and the popular native libraries to the
point where most apps run without a problem is still in progress. Peach can
drive a good share of everyday development today, and large apps may still hit
gaps. peach compat tells you, before you open your
app, which of its packages Peach runs and what is missing.
Beyond development
- +Shareable previews. Record a flow and hand anyone a link to your real, interactive app. See Preview uploads and sharing.
- +Pull request previews. The Peach GitHub App posts a recording and a live preview on every pull request. See GitHub PR previews.
- +App Store screenshots. Pose your app, add copy and colors, and export the sizes you need. See App Store screenshots.
- +3D demos. Put the phone on a 3D stage and record it with
peach mode three.