Flitzdocs

Introduction

What Flitz is, what it is not, and where to start.

Optimized for AI agents

These docs are written to work well with AI coding agents. Don't hesitate to paste a link to them — docs.flitz.dev — into your favorite agent, or use the Open menu at the top of every page to talk to the docs in the platform of your choice.

Flitz lets a Flutter team see work-in-progress changes on a real device seconds after a developer makes them — without rebuilding the app, reinstalling it, or going through a store round-trip.

It works by splitting your app in two. The host is your own app with the Flitz loader embedded: the compiled Dart runtime, the Flutter engine, and every native plugin you use. The bundle is your Dart code — your app, its Dart packages, and the Flutter framework — compiled to portable bytecode and packaged with your assets as a .flitz archive. flitz publish builds a bundle from your project and prints a link; a teammate opens the link on their device, and the host downloads the bundle and runs it — the same app, just arriving through a link instead of through a build.

For development and testing

Flitz runs in your development and test loop only — your production build ships the normal way and is never touched.

What Flitz is not

  • Not code push. A bundle is a complete app build, never a patch to a released app.
  • Not hot reload. Flitz changes how your team sees work, not the inner loop on your machine.
  • Not a performance preview. Your Dart code runs interpreted while the engine and rendering stay compiled, so the UI feels close to normal but heavy pure-Dart work runs noticeably slower than in your release build.
  • Not for untrusted code. A bundle runs with the full privileges of the host. Flitz is for your own team's bundles.

Where to go next

On this page