ZapbirdDocs

How Zapbird works

What happens between saving a file and seeing it on your phone.

Zapbird splits your setup in two: a small server on your computer and the runner app on your phone. They talk over your local network.

#The parts

PartWhere it runsWhat it does
zapbirdYour computerStarts the server, watches your files, compiles your app and prints the QR code.
Runner SDKYour computerThe compiler files that match one build of the runner on your phone.
Zapbird runnerYour phonePairs with the server and runs your app.

#When you save

  • The file watcher notices the change.
  • The server compiles your project to bytecode.
  • The phone downloads the new code and checks it before using it.
  • The runner applies the change, keeping your app state for supported edits.

#Two ways to run

ModeNeedsBest for
BytecodeA runner SDKThe fast path. Every save updates the phone by itself.
KernelNothing extraFull Flutter. Press r to reload and R to restart.

With a runner SDK installed, zapbird start picks bytecode on its own. See the start command.

#What stays on your computer

The phone receives compiled bytecode and your assets, not your source files, unless you turn on phone editing. Read Security.

Was this doc helpful?

Zapbird sends no analytics. Read about security.

Flutter and the related logo are trademarks of Google LLC. Zapbird is not endorsed by or affiliated with Google LLC.

esc