Ionic stopped selling Appflow in February 2025, and its help center says every Appflow feature and service will be sunset on 31 December 2027. It asks customers to move their native builds and live updates elsewhere by then, and warns that apps still relying on Appflow at that point may see build pipeline failures and live update failures. Ionic Framework and Capacitor themselves carry on, so your app’s framework does too. The pipeline around it is what needs a new home.
VibeView takes over the builds and adds what Appflow didn’t have: one CLI command runs your web
build, npx cap sync and the native build for iOS and Android, signs the release
with credentials you bring or VibeView generates, and uploads it to TestFlight or Google
Play. Then the simulator build opens on a cloud iPhone or Android phone in your browser,
ready to share with someone who has no account, test with recorded flows or hand to a
coding agent. Live updates are the one part it doesn’t cover.
Try your first build before you plan the migration
npm install -g vibeview, then vibeview build --cloud --platform all
from your Capacitor project. The CLI suggests the commands, and the finished builds open
on a cloud device. 15 cloud builds a month are included on the free tier.
Ionic Appflow alternatives: how VibeView compares
| What you are deciding | VibeView | Ionic Appflow |
|---|---|---|
| Can you sign up today? | Yes — every plan, including a free one with 15 cloud builds a month; beyond the included builds, a flat $1.50 per iOS and $0.75 per Android build on paid plans | No — Ionic discontinued new sales in February 2025; existing customers keep access through 31 December 2027 |
| Can you open the native build on a cloud device? | Yes — every simulator and emulator build opens on a cloud iPhone or Android phone in the browser; share it as a link with someone who has no account | Its docs describe browser previews of the web build and installing native builds on a phone; no cloud simulator or emulator is described |
| Can it test the app after the build? | Yes — record a flow in the browser and replay it on every build, with an AI agent (beta) for a moved button and a screenshot check after every step, from CI or a schedule | Not described in the Appflow documentation we checked |
| Can it build the iOS app without a Mac? | Yes — the web build, cap sync ios and the Xcode build run on a managed macOS toolchain, from Windows, Linux or a Mac | Yes — native iOS and Android binaries are built in the cloud |
| Can it publish to the App Store and Google Play? | Yes — vibeview submit uploads to TestFlight or a Play track, from the CLI or the dashboard | Yes — publishing to both stores from the Appflow dashboard |
| Live updates without a store release? | No — VibeView ships native binaries only | Yes — live updates and hotfixes, in Capacitor and Cordova apps |
| Which projects? | Capacitor and Ionic, React Native and Expo, Flutter, Kotlin Multiplatform and native Xcode or Gradle, with suggested commands; Cordova untested | Capacitor, Cordova, React Native and native iOS and Android |
The first three rows decide it, and VibeView wins all three: you can still sign up, the build opens on a cloud device, and it can be tested there. The build and the store upload are ties, each side builds a framework the other doesn’t, and Appflow keeps one clear advantage: live updates.
Moving your builds over
- Commit the native projects. Keep the
android/andios/folders thatnpx cap addcreates in git; the build syncs your web app into them. - Run the first build.
vibeview build --cloud --platform allsuggests the commands for your project — your web build,cap sync, then Gradle on the right Java or Xcode — and saves them tovibeview.json. - Bring your signing material.
vibeview credentials addtakes your existing keystore,.p12and provisioning profile, orvibeview credentials generatemakes new ones. An app already on Google Play keeps signing with the same upload key. - Ship. Add the signing block the App Signing docs show to your Gradle file, then
vibeview build --cloud --productionandvibeview submitto TestFlight or a Play track. An iOS release archives with a command you write once; the guide shows it. Starting builds from your existing CI is one step: install the CLI and run the same command. - Decide on live updates. If your app depends on them, choose a live-update service for that part; VibeView doesn’t replace it.
When is Appflow still the better choice?
Live updates, and the setup you already have — until 2027.
Appflow does live updates, and VibeView doesn’t. If your release process leans on pushing web changes without a store review, that part needs another service whatever you choose for builds. And if your Appflow pipeline works today, nothing forces a move before the end of 2027. Move when it suits you, but test the new build path before the deadline does it for you.
Frequently asked questions
Is Ionic Appflow shutting down?
Ionic says so. It stopped selling its commercial products, Appflow included, on 11 February 2025, and its help center says all Appflow features and services will be sunset effective 31 December 2027, warning that apps still relying on Appflow then may see build pipeline failures and live update failures. Ionic Framework and Capacitor themselves continue.
Can VibeView replace Appflow’s native builds?
For Capacitor and Ionic apps, yes. vibeview build --cloud installs your dependencies, runs your web build, syncs it with npx cap sync and builds the iOS app on a managed Mac and the Android app with the right Java, from Windows, Linux or a Mac. Production builds are signed with credentials you upload or VibeView generates, and vibeview submit uploads them to TestFlight or a Google Play track. The CLI suggests the Android release command; an iOS release archives with a command you write once, which the guide shows.
Does VibeView do live updates?
No. VibeView builds, signs and submits native binaries and runs them on cloud devices; it doesn’t push web-layer updates to installed apps. If you rely on Appflow’s live updates, you need a separate live-update service for that part of the migration.
Can I keep my existing signing certificates and keystore?
Yes. Upload your Android keystore and your iOS .p12 certificate and provisioning profile with vibeview credentials add, or let VibeView generate new ones: an Android keystore with one command, and the iOS certificate and profile through Apple’s API with an App Store Connect key. For an app already on Google Play, keep signing with the same upload key.
Does it work for Cordova apps?
The CLI suggests build commands for Capacitor projects, not Cordova. A cloud build runs any shell command you give it, so a Cordova project whose tools install from the build command may build too, but we haven’t tested it. Capacitor is the route Ionic itself maintains.
One build tells you whether it fits
Run vibeview build --cloud on your Capacitor project on the free tier, open
the result on a cloud device, and compare it with the build you got from Appflow.
Published 16 October 2026 · Ionic’s announcement, help center and Appflow documentation verified 16 October 2026