Pear DocsStart from a template
Two official Pear boilerplates to start from—hello-pear-electron for desktop GUI apps and hello-pear-bare for standalone terminal binaries, both 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 clone an official boilerplate and learn where each piece lives. Both embed pear-runtime for peer-to-peer over-the-air updates—pick the one that matches what you're shipping.
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 (terminal)
A standalone Bare executable: CLIs, daemons, and tools with no GUI and no peer dependencies.
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 CLI, daemon, or other headless tool? Start from hello-pear-bare—it compiles to a single standalone binary per OS and architecture.
Both share the same peer-to-peer core: the Bare runtime, pear-runtime for updates, and the Hyperswarm + Corestore stack. Your peer-to-peer logic is portable between them—only the shell (GUI versus terminal) changes. See Runtime and languages.
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.