Skip to content

Flitz for software engineers

Publish it. Share it. Move on.

Flitz builds a preview straight from your branch and gives you a link or a QR code to share – so feedback arrives before the PR, not three days after it.

I finished it an hour ago. It's still sitting in a PR, waiting on CI.

PR review, CI, sign-and-upload, distribution – today, that's the only path to getting feedback on your work. Hours, sometimes days, before anyone actually sees it. And when the feedback finally arrives, you've already moved on to something else – so you drop what you're doing, work out how the code you wrote days ago fits together again, and start over.

Your workflow with Flitz

  1. 1

    Make your change

    You work on the same branch, in the same workflow you already have. Nothing about how you write code changes.

  2. 2

    Run a preview

    You get a preview of your app and a link or QR code to go with it, in about a minute. No CI run to clear first.

  3. 3

    Share the link in Slack, email, wherever

    You paste it into Slack, email, wherever your team talks. Anyone who needs to see the feature opens it on their own phone, and you hear back before the PR is even up.

Feedback in minutes, not days

Same pipeline, same branch. The only thing that moves is where the first feedback happens.

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.

What you actually integrate

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.

What Flitz changes for you

Publish straight from your branch

Whatever's on your branch – finished or not – becomes a real, running app with one command. No PR required to show it. Without waiting for CI.

One link replaces every request for a version

Everyone who needs to see it – a designer, a PO, a tester – opens the same link or scans the same QR code, and gets your actual, stateful app running on their own device.

Instant feedback

Feedback arrives while you're still in the code, so a correction is a few minutes of work instead of a return trip days later. Less time spent re-reading what you already wrote, more features closed per sprint.

See how it looks for the rest of your team

Your questions, answered

Does it work with my existing CI/CD?

Yes. Flitz complements CI/CD, it doesn't replace it. Your full pipeline still runs once, on a version that's already been checked out on a real device.

Do reviewers have to reinstall the app for every preview?

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.

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 version never ends up on a public URL.

Can we host previews ourselves?

Yes. You can run Flitz on your own hosting, with support to fit it into your existing infrastructure and review policies.

Stop waiting on the pipeline to get feedback

Publish a preview from your branch and get feedback the same day, from a phone rather than a screenshot.