VibeView starts where a build service stops: the device. A cloud build compiles your Flutter, React Native, Capacitor or native app without a Mac of your own, signs it and submits it, and the simulator build lands on a cloud iPhone, Android phone, Apple TV or Android TV that you open in a browser, share with someone who has no account, test with recorded flows and hand to your coding agent. The device time comes from your plan’s included minutes, not a separate product, and sessions run as long as you need them on paid plans.
Codemagic, a CI/CD service that started with Flutter, builds and signs just as well, and it added an in-browser simulator, App Preview, as a paid extra for teams. The table below is about what happens to the build after it compiles: who can open it, for how long, on which devices, and what tests it.
Build your Flutter app once, from wherever you are
npm install -g vibeview, then vibeview build --cloud --platform all
from your project root. The CLI suggests the Flutter commands, FVM pin included, and the
finished builds appear in your app, ready to run. 15 cloud builds a month are
included on the free tier.
Codemagic alternatives: how VibeView compares
| What you are deciding | VibeView | Codemagic |
|---|---|---|
| Can you open the build on a cloud device? | Yes, included — every simulator build opens on a cloud device, drawing on your plan’s streaming minutes: 1,000 a month on the $19 Dev plan, with no session length limit, 2 devices at once | With App Preview, a paid extra for teams: $0.095/min after a 100-minute trial, or $3,000/year for unlimited minutes; sessions of up to 20 minutes, one at a time by default |
| Can someone outside your team open it? | Yes — an app share link opens on a live device for anyone with the link, no account needed, or embed the device in a web page | Their docs describe preview links for teammates, and build dashboards that share builds and artifacts with people outside Codemagic |
| Does it cover TV apps? | Yes — Apple TV and Android TV builds are signed and submitted like phone builds and run on cloud TV devices with a d-pad (Flutter targets Android TV only). Roku channels run on real Roku hardware | App Preview’s documentation describes an iOS simulator and an Android emulator; no TV platform is mentioned |
| Can it test the app after the build, on the same device? | Yes — record a flow in the browser and replay it, hand a moved button to an AI agent (beta), compare screenshots after every step, from CI or a schedule | Your own tests run during the build on an iOS simulator or Android emulator, plus integrations with third-party device-testing services |
| Can it build a Flutter iOS app without a Mac on your desk? | Yes — vibeview build --cloud runs it on a managed macOS toolchain with the Flutter SDK, from Windows, Linux or a Mac | Yes — Flutter builds run as workflows defined in codemagic.yaml, on Mac mini machines |
| Does it follow your FVM pin? | Yes — FVM is installed; a build command that runs fvm flutter uses your committed .fvmrc, and the CLI suggests it | Yes — set the Flutter version to fvm and it is read from .fvmrc (or the older fvm_config.json) |
| Will it handle iOS signing for you? | Yes — with an App Store Connect API key, vibeview credentials generate creates the certificate and provisioning profile; Android keystores are generated too | Yes — with an App Store Connect API key, automatic code signing fetches or creates the certificate and profile |
| Can it publish to TestFlight and Google Play? | Yes — vibeview submit or the dashboard’s Submit to store button | Yes — TestFlight and Google Play publishing from the workflow |
| Which frameworks? | Flutter, React Native and Expo, Capacitor and Ionic, Kotlin Multiplatform, native Xcode and Gradle — and other projects whose tools install from the build command | Flutter, React Native, native iOS and Android, Ionic Capacitor and Cordova, Kotlin Multiplatform, Unity and .NET MAUI |
| What does a build cost? | Included builds on every plan (15 on Free, 25 on Dev); beyond them, a flat $1.50 iOS / $0.75 Android per build on paid plans ($2 / $1 on Free) | 500 free macOS M2 minutes a month on the single-user free plan; then $0.095/min on a Mac mini M2, $0.045/min on Linux |
| Over-the-air updates? | No — VibeView ships native binaries | Yes, for React Native — CodePush by Codemagic, from $1 per 2,500 installs |
| Can builds start on every push? | From your existing CI: run vibeview build --cloud as a step, and a signed webhook reports the result | Yes — workflows are a CI/CD pipeline of their own |
The first four rows are what happens to the build after it compiles, and VibeView wins each of them. The four after that are ties on the build itself. Codemagic is ahead on the last four: more frameworks, per-minute pricing that suits short builds, over-the-air updates for React Native and a pipeline that starts on its own.
What you get beyond the comparison table
The device is part of the plan
Every plan includes streaming minutes, and a simulator build is one click from a running session. On paid plans it comes out of your included minutes, with no 20-minute timer on looking at your build.
A link for people with no account
Send a client, a tester or a designer an app share link and they tap through the build on a live device in their browser. Turn on sign-in when the link goes somewhere public.
Tests that survive a redesign
Record a flow once and replay it on every build. When a button moves, an AI agent (beta) finds it by name and carries on, so one design change costs one step, not a red suite.
Built for coding agents
A Claude Code skill and an MCP server let an agent build your app, install it on a cloud device, tap through it and check its own work, from the same CLI you build with.
When is Codemagic the better choice?
A full pipeline, per-minute pricing, more frameworks.
If you want builds that start on every push, run your own tests and publish on
their own, Codemagic is a pipeline and VibeView is not. Its per-minute price suits short
builds, its free plan has 500 macOS minutes, it sells over-the-air updates for React
Native, and it builds Unity and .NET MAUI apps, which we don’t. Buy VibeView for what
happens to the build afterwards: a device anyone can open, TV included, and tests that
run on it. You can keep Codemagic for the pipeline and send its builds to VibeView with
vibeview upload-app.
Frequently asked questions
Is VibeView a Codemagic alternative for Flutter?
Yes. vibeview build --cloud compiles a Flutter app for iOS and Android without a Mac of your own, honours an FVM pin, generates signing credentials and uploads to TestFlight or a Play track. Then the build opens on a cloud iPhone or Android phone that anyone can reach from a link, and your recorded tests and coding agent run on that same device.
Which is cheaper per build?
It depends on how long your builds run. Codemagic bills by the minute ($0.095 on a Mac mini M2, $0.045 on Linux), so a short build is cheaper there; a VibeView build is a flat $1.50 for iOS and $0.75 for Android on paid plans however long it runs, up to the build time limit, and every plan includes some (25 a month on Dev). The bigger cost difference is after the build: opening it on a device is part of a VibeView plan, while App Preview minutes are billed on top.
Codemagic has App Preview. How is VibeView different?
Codemagic’s App Preview runs your build on an in-browser iOS simulator or Android emulator too. Its docs say it is for teams only, billed at $0.095 a minute after a 100-minute trial (or $3,000 a year for unlimited minutes on a fixed plan), with sessions of up to 20 minutes and one at a time by default. On VibeView, device time comes out of your plan’s streaming minutes (1,000 a month on the $19 Dev plan, with no session length limit), a share link opens for someone with no account, and the same device runs your recorded tests, Apple TV and Android TV included.
Does VibeView support FVM like Codemagic?
Yes. The builders have FVM, so a committed .fvmrc picks the Flutter release when the build command runs fvm flutter, and the CLI suggests that command when it finds the pin. Flutter 3.47.7 and 3.44.9 are ready; another release installs during the build.
Can VibeView start builds on every push like a CI service?
Not by itself today. You start a cloud build from the CLI, from your coding agent, or as a step in your existing CI (GitHub Actions, GitLab CI or anything that runs a command), and a signed webhook tells your systems when it finishes. Codemagic’s workflows are a full pipeline of their own.
One build tells you which is yours
Run vibeview build --cloud on the free tier, open the result on a cloud
device, and send the link to one person who would otherwise have asked you for the file.
Published 16 October 2026 · Codemagic pricing, documentation and changelog verified 16 October 2026