Introduction
What Flitz is, what it is not, and where to start.
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 application code, compiled to
portable bytecode and packaged as a .flitz archive. flitz publish builds a
bundle from your project; the host downloads it and runs it — the same app,
just arriving over the air instead of through a build.
Experimental
Flitz is built on Dart's upstream-experimental Dynamic Modules. It 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 for untrusted code. A bundle runs with the full privileges of the host. Flitz is for your own team's bundles.