Integrations

Four kinds of integration

They are not variations on one thing, so it is worth knowing which one you are looking for before you pick a page.

Getting results out. GitHub Actions runs your tagged test groups on a live device from a workflow and reports back on the pull request, so a regression blocks a merge rather than surfacing a week later. GitLab CI and CircleCI run the same commands and show the results as a JUnit report. Slack puts the same results — plus visual regressions and quota warnings — in the channel your team already watches.

Getting your build in. The GitHub App builds your app in the VibeView cloud on every push and pull request, with no workflow to write, and links each build to a live device from the pull request. React Native covers the live loop: your local Metro bundler attached to a cloud device, so a saved file shows up on the device a second later. Expo covers the EAS build profile that actually produces an uploadable artifact — and the one that looks right and is not. Flutter is the short one, because Flutter needs no special handling beyond building for the simulator.

Getting it to the stores. App Store Connect & TestFlight takes one App Store Connect API key and sends your iOS and Apple TV builds to TestFlight groups and Beta App Review, then follows each build until it reaches your testers. Android and Android TV builds go to Google Play, and Fire TV builds to the Amazon Appstore, with the same submit command. Roku channels are tested and shared in VibeView and published from Roku's Developer Dashboard.

Letting an agent drive. Claude Code, Cursor and Codex — or any agent with terminal access, or any MCP client — can use the CLI or its MCP tools to run your app on a device and read structured results back, closing a loop that otherwise runs through you describing what happened. Their pages cover each client's own setup.

If yours is not listed

It very likely still works. None of these are adapters we had to build — underneath every page on this list is a published command-line tool and a REST API. Bitrise, Jenkins and any other CI that can run shell commands work the same way. The pages exist because each tool has its own quirks worth writing down, not because the others are unsupported.

The CI/CD integration guide is the place to start — it walks the whole pipeline from producing a build to reading results. The CLI reference covers every command and flag, and CI testing covers tagging groups and running them from any CI.