Skip to content

Preview environments for Flutter apps

Show your work on a real device
– in under 3 minutes

Getting a working build in front of a designer, PO, or stakeholder shouldn't take a PR, a CI run, and a TestFlight upload. With Flitz, you push a preview from your dev machine and they open it on a real phone – in minutes, not days.

Push a preview. Share a link. Done.

  1. 1

    Make a change

    Work on your branch as you always do – your codebase, your packages, your Flutter version.

    • Flutter 3.41+
    • iOS & Android
    • Native plugins included
  2. 2

    Publish a preview

    Run the Flitz CLI to publish a version – straight from a developer's machine, any state of progress.

    • No PR required
    • No CI run
    • ~1 min
  3. 3

    See it live

    Send the link to a designer, PO, or tester. They open the real app on their own device. You get real feedback before the code ever hits a PR.

    • QR or link
    • Real devices
    • Specific people only

Feedback in minutes, not days

The process today1 day
  1. 01Change completed
  2. 02PR review & approval
  3. 03CI / CD pipeline
  4. 04Build distribution
  5. 05Stakeholder review
With Flitz~3 minutes
  1. 01Change completed
  2. Feedback02PR review & approval
  3. 03CI / CD pipeline
  4. 04Build distribution
  5. 05Stakeholder review

99% less time to feedback.

One preview link, and everyone on the team gets what they need

See it running, not just rendered

The developer writes the code and builds the app – you're the one who needs to see how it actually turned out, fast. Instead of waiting for it to work down the pipeline, open the preview on a real device the same day it's built and check the running app against your design.

  • See the real look & feel on real hardware – real fonts, motion, and gestures, not a static export
  • Catch the gaps between your design and the build early, while they're still cheap to fix
  • React the day it's built, not after it's merged

Everything to publish and share a preview

Flitz SDK

A modified version of the Flutter SDK – 3.41 and up – that powers your preview builds.

Flitz CLI

Command-line tooling for publishing your work – build and push a preview from your branch.

Native plugins

Drop-in native plugins to embed in your application so it can load and run preview bundles.

Hosting platform

A hosting platform for the bundles – stores and serves every preview behind a shareable link.

One tool for any team size

Whether you're two people shipping your first app or a hundred developers across squads, Flitz scales to the way you work.

Startups & small teams

Show your work the moment it runs

You just want the people who care to see what you're building, right now. With Flitz you share a running preview as soon as it works, and whoever's reviewing opens it and reacts on the spot.

  • See results early, not after a long PR process
  • No pipeline to set up – a one-time Flitz integration, then publish from day one
  • More feedback rounds per feature, no more waiting for builds to finish

Enterprise & large orgs

Scale across every squad

Give dozens of teams a consistent preview workflow that slots alongside your existing CI/CD, review process, and security requirements.

  • Custom hosting and support for security-conscious orgs
  • One consistent preview workflow across every squad
  • Complements your CI/CD and release governance, never replaces it

Questions, answered

Do I need to change my app's architecture to use Flitz?

No. You keep your codebase, your packages, and your project structure. You switch to the Flitz Flutter SDK, add the native plugins once, and publish previews from your existing branches.

Does this replace our CI/CD or TestFlight and Play Console?

No, and it isn't meant to. Flitz covers the gap before a PR – the fast, throwaway previews you share while a feature is still taking shape. Your release pipeline and store distribution stay exactly as they are.

Which Flutter versions are supported?

Flutter 3.41 and up, on both iOS and Android. Native plugins are supported, so previews behave like the real app rather than a stripped-down web build.

How long does a preview take to publish?

Around a minute from a developer's machine – no PR, no CI run, no review queue. Reviewers open the link, and the new bundle loads into the app they already have installed.

Who can open a preview link?

Only the people you share it with. Previews are scoped to specific recipients inside your organization, so an internal build never ends up on a public URL.

Do reviewers have to reinstall the app for every build?

No. They install the host app once, then every new preview loads into it. Opening a second, third, or tenth preview is a single tap.

Can we host previews ourselves?

Yes. Larger and security-conscious organizations can run Flitz on custom hosting, with support to fit it into existing infrastructure and review policies.

When can we start using it?

Flitz is in early access. Request access and we'll get in touch to set up your first preview together.

Stop waiting on builds to get feedback

Push a preview from your machine and get real reactions on real devices the same day.