Glossary
The words Zapbird uses, in one place.
These are the terms used across the docs.
| Term | Meaning |
|---|---|
| zapbird | The command on your computer. It starts the server, watches your files, compiles your app and prints the QR code. |
| Runner | The Zapbird app on your phone. It pairs with the server and runs your app. |
| Runner build | The build number the runner shows in its Settings. The SDK you need matches it. |
| Runner SDK | The compiler files that match one build of the runner. Install it with zapbird sdk install. |
| Bytecode mode | The fast mode. It needs a runner SDK, and every save updates the phone by itself. |
| Kernel mode | The full Flutter mode. It needs no SDK. You reload with r and restart with R. |
| Pairing | Connecting a phone to the server with a QR code, a typed address or a link, and approving the project. |
| QR code | The code zapbird start prints. It carries the server address, a secret and the server certificate. |
| Pairing code | The 6-digit code the phone shows when you type an address instead of scanning. Type it in the terminal to allow the phone. |
| Doctor | zapbird doctor: checks the network address, the project, Flutter, the SDK, your packages and your keys. |
| Trusted Flutter apps | A runner setting that lets the runner run a full Flutter app. Turn it on only for projects from your own trusted computer. |
| zapbird.yaml | The file beside your app that turns your project permissions into store-ready entries. See zapbird.yaml. |
| Tailscale | An optional network the phone can use to stay connected on any Wi-Fi. Turn it off with --no-tailscale. |