Grab any branch on demand
Every preview is labelled with the branch it came from, so you always know what you're testing. No guessing which version in the channel has the fix.
Flitz for QA engineers
Test the change the moment it's ready
Test any branch on a real device, on iOS and Android, minutes after the change was written. No merge, no release build, no guessing which build has the fix.
I don't know which version I'm testing, or when the next one arrives.
Verifying one change means waiting for a merge, a pipeline run and a distribution upload – then working out which version in the channel actually contains it. Testing starts hours or even days after the code was written, and every retest costs the same wait again.
Your workflow with Flitz
1
Choose the preview you need
Published straight from the developer's branch, minutes after the change was written.
2
Load it on your device
Open the link or scan the QR code, and it loads in the host app you already have installed, on iOS or Android.
3
Report against a version everyone can open
Attach the preview link to the ticket – the developer reproduces it on the exact version you tested, the same day.
Feedback in minutes, not days
Your release pipeline and full regression stay exactly where they are. What changes is how soon a change first reaches a real device.
The process today1 day
- 01Change completed
- 02PR review & approval
- 03CI / CD pipeline
- 04Build distribution
- 05Testing
With Flitz~3 minutes
- 01Change completed
- Testing02PR review & approval
- 03CI / CD pipeline
- 04Build distribution
- 05Testing
99% less time to feedback.
What Flitz changes for you
Retest without a reinstall
Install the host app once. Every new preview – the fix, the retest, the next branch – loads into it with a single tap.
Reproduce on both platforms
Edge cases behave the way they do for your users, because a preview runs on real iOS and Android hardware with the native plugins and state intact.
See how it looks for the rest of your team
Software engineer
publishes straight from a branch, without a PR or a CI run first.
Learn more – Software engineerProduct owner
sees and approves the real, running feature the same day it's built.
Learn more – Product ownerYour questions, answered
Do I have to reinstall the app for every preview?
No. You install the host app once, then every new preview loads into it. Opening a second, third, or tenth preview is a single tap.
Can I test a branch that hasn't been merged?
Yes, that's the point. A developer publishes a preview from any state of their branch, so you can verify a change before it reaches a pull request.
How do I know which version I'm testing?
Every preview is a labelled link tied to its branch, so the version under test is unambiguous – and you can attach that same link to a ticket.
Does a preview behave like the real app?
Yes, it's your real, stateful app with the native plugins already in it, running on iOS and Android.
Does this replace our CI/CD pipeline?
No. Your pipeline stays exactly as it is. Flitz adds a faster path to a testable version, so problems surface before the pipeline spends time on them.
Stop waiting on the pipeline to start testing
Load any branch onto a real device and verify the change the day it was written.