P2P DocsStart from a template
Official Pear boilerplates to start from—hello-pear-electron for desktop GUI apps, hello-pear-bare for long-running terminal binaries, hello-pear-daemon for short-lived CLIs, hello-pear-qvac-tui for on-device AI in the terminal, and hello-pear-react-native for mobile apps—all with peer-to-peer over-the-air updates. Pick the one that matches what you're shipping.
The fastest way to a production-shaped app is to copy an official starter project—a boilerplate you clone and change—and learn where each piece lives. Every template embeds a pear-runtime-family module for peer-to-peer over-the-air updates—pick the one that matches what you're shipping.
New to the CLI? Run pear --menu (Pear 3.2.0+) to browse every command from a filterable list and fill in its flags as a form, instead of memorizing them. See Browse commands with the interactive menu.
hello-pear-electron (desktop)
An Electron GUI app: renderer ↔ main ↔ Bare worker behind a preload bridge. The shape Keet and PearPass ship.
hello-pear-bare (long-running terminal)
A standalone Bare executable for long-running programs: services, REPLs, and TUIs with no GUI and no peer dependencies.
hello-pear-daemon (short-lived CLI)
A standalone Bare executable for commands that run and exit: a detached bare-daemon updater checks for updates in the background after the command returns.
hello-pear-qvac-tui (on-device AI terminal)
A terminal app that runs a language model on the user's own machine: two Bare workers, one for updates and one for QVAC inference, behind a bare-tui interface.
hello-pear-react-native (mobile)
An Expo/React Native app: a Bare worklet embedded via pear-mobile, with the same over-the-air updates. The mobile counterpart to hello-pear-electron.
Which one?
- Building a desktop GUI? Start from hello-pear-electron—it ships a renderer and the preload bridge that connects your UI to peer-to-peer logic in a Bare worker.
- Building a long-running headless program—a service, REPL, or TUI? Start from hello-pear-bare—it compiles to a single standalone binary per OS and architecture and keeps your peer-to-peer code in a Bare worker.
- Building a short-lived CLI that runs and exits? Start from hello-pear-daemon—the same standalone binary, but the update check runs in a detached daemon so the command never blocks on the network.
- Building a terminal app that runs an AI model on the user's machine? Start from hello-pear-qvac-tui—it adds a QVAC inference worker and a
bare-tuiinterface to the hello-pear-bare shape. - Building a mobile app? Start from hello-pear-react-native—it embeds a Bare worklet in an Expo/React Native app via
pear-mobile.
They share the same peer-to-peer core: the Bare runtime, a pear-runtime-family module for updates (pear-runtime on desktop and in the terminal, pear-mobile on mobile), and the Hyperswarm + Corestore stack. In the worker-based templates—hello-pear-electron, hello-pear-bare, hello-pear-qvac-tui, and hello-pear-react-native—your peer-to-peer logic is portable and only the shell (GUI, terminal, or mobile) changes. hello-pear-daemon has no worker, so its only peer-to-peer code is the update client. See Runtime and languages.
Once you've cloned a template and made it yours, ship it over the air. For desktop and terminal, Deploy your application is the step-by-step release flow, and Release pipeline explains the stage → provision → multisig model behind it. Mobile shares that stage/provision/multisig model but builds a different payload—see Deploy your mobile application.
More hello-pear repositories
Two more repositories sit alongside the templates, but they aren't starting points for a whole app: one is the backend the templates share, the other an early worker-based CLI sample.
hello-pear-worker (shared worker)
The worker the electron, bare, react-native, and qvac-tui templates embed: pear-runtime or pear-mobile updates, Hyperswarm, Corestore, and framed IPC. Install it from npm or copy it into your app's workers/main.js.
hello-pear-bare-worker (early worker-based CLI)
A single-file Bare CLI around the same workers/main.js that hello-pear-bare shipped when it became worker-based in June 2026. Start from hello-pear-bare instead.
Where to go next
- Build a peer-to-peer chat—build the desktop app up from scratch instead of cloning.
- Pear desktop application architecture—the renderer/main/worker model behind the Electron template.
- Runtime and languages—where Bare and the runtimes fit across desktop, terminal, and mobile.
Last updated on