Passer au contenu

Migrer from AppFlow to Capgo

🚦 Ionic announced that AppFlow’s commercial products—including Mises à jour en direct—are winding down. Existing projects can run until 31 December 2027, but no Nouveau customers are accepted and no Nouveau Fonctionnalités are planned. This Guide walks you through the actions required to Migrer to Capgo and highlights the Natif automation you gain.

Capgo handles channels, bundle retention, rollbacks, analytics, and CLI uploads for you. Migration boils down to installing the plugin, calling CapacitorUpdater.notifyAppReady(), and—if desired—configuring optional manual controls. The sections below walk through each task directly.

Step 0 – Capture your current AppFlow Configuration

Section titled “Step 0 – Capture your current AppFlow Configuration”
  • Remarque your AppFlow Application ID, existing Canaux, and signing keys.
  • Exporter any Bundle history you want to archive.
  • If you are using GitHub Actions or another CI provider, keep those pipelines—they will keep working with Capgo.

Step 1 – Replace the AppFlow SDK with Capgo

Section titled “Step 1 – Replace the AppFlow SDK with Capgo”
Terminal window
npm uninstall @capacitor/live-updates
npm install @capgo/capacitor-updater
npx cap sync

That’s it. Capgo Bundles the Natif code for both iOS and Android; no extra JavaScript helpers are required.

Step 2 – Minimal Configuration (no manual fields)

Section titled “Step 2 – Minimal Configuration (no manual fields)”

The existing Configuration block is extensive. Capgo auto-detects your project and Canaux, so the minimal Configuration is:

capacitor.config.ts
import { CapacitorConfig } from '@capacitor/cli'
const config: CapacitorConfig = {
plugins: {
CapacitorUpdater: {
autoUpdate: true,
autoDeletePrevious: true,
},
},
}
export default config
Ionic AppFlow settingCapgo equivalentDo you need to set it?
appIdManaged in the Capgo dashboardAutomatically supplied when you create the project
channel / defaultChannelChannel rules in the dashboard/APIOptional override; defaults come from the server
autoUpdateMethodautoUpdate: trueEnabled by default
maxVersionsRetention policyConfigured centrally (1 month default, 24 months max)
enabledNot requiredCapgo toggles availability per channel

Step 3 – Call notifyAppReady() (the only required hook)

Section titled “Step 3 – Call notifyAppReady() (the only required hook)”

In Ionic’s guide you wire sync, download, and reload, then hide the splash screen manually. Capgo performs those actions natively. You only need to confirm the app is ready:

import { CapacitorUpdater } from '@capgo/capacitor-updater'
CapacitorUpdater.notifyAppReady()

If the confirmation never arrives, Capgo rolls the Bundle Retour automatically.

That’s it—Capgo handles the background checks, splash visibility, and rollbacks for you.

Optional: run logic before the splash screen hides
import { CapacitorUpdater } from '@capgo/capacitor-updater'
import { SplashScreen } from '@capacitor/splash-screen'
CapacitorUpdater.addListener('appReady', () => {
// Log diagnostics or run custom code if needed
SplashScreen.hide()
})
CapacitorUpdater.notifyAppReady()

Step 4 – Mise à jour strategies translated

Section titled “Step 4 – Mise à jour strategies translated”

AppFlow documents three strategies. Here is how they map to Capgo:

  • AppFlow: configure autoUpdateMethod = background, call sync() manually.
  • Capgo: enabled by default. No JavaScript required.
  • AppFlow: add an App.addListener('resume') handler that downloads and reloads.
  • Capgo: auto-Mise à jour runs on resume already. Ajouter the handler only if you want a custom timing window.
Optional: manual resume check
import { App } from '@capacitor/app'
import { CapacitorUpdater } from '@capgo/capacitor-updater'
App.addListener('resume', async () => {
const bundle = await CapacitorUpdater.download()
if (bundle) {
await CapacitorUpdater.set({ id: bundle.id })
}
})
  • AppFlow: prompt the user and call reload().
  • Capgo: mark the bundle as “mandatory” in the dashboard, then listen for the majorAvailable event (emitted after notifyAppReady()) to prompt or force users inside your app.
AppFlow methodCapgo equivalentDo you need it?
LiveUpdates.sync()Handled automaticallyCapgo’s native auto-update runs without a manual sync call
LiveUpdates.download()CapacitorUpdater.download()Optional for custom flows
LiveUpdates.reload()CapacitorUpdater.set()Optional; dashboard toggles handle forced updates
LiveUpdates.getVersion()CapacitorUpdater.current()Optional diagnostics

Step 6 – Déployer using the Capgo CLI or API

Section titled “Step 6 – Déployer using the Capgo CLI or API”

Finish the Migration by uploading Bundles with the Capgo CLI or API. The workflow mirrors what you may have scripted before, but now includes Natif safeguards:

Terminal window
capgo login # authenticate once
capgo bundle upload \
--path dist \
--channel production # automatically tags platform/version

Capgo automatically:

  • Keeps Appareil-level audit Journaux for every Installer.
  • Sends proactive emails when you approach plan limits.
  • Provides burst credits so you are never blocked mid-Libération.
  • Publishes latency metrics for 18 global regions at status.capgo.Application/history.

Why is AppFlow shutting down Mises à jour en direct?

Section titled “Why is AppFlow shutting down Mises à jour en direct?”

Ionic is discontinuing commercial products, including AppFlow, to focus on their open-source framework. Existing customers can continue using Mises à jour en direct until 31 December 2027, but no Nouveau Fonctionnalités or customers are accepted. Capgo fills that gap with a dedicated Natif OTA platform.

Most teams complete the move in under a day. Concepts such as channels, deployments, and release rules map directly, and our team provides documentation plus hands-on support. In many cases you simply install the plugin, call notifyAppReady(), and upload your first bundle.

Yes. AppFlow Mises à jour en direct Démarrer at $499/mo. Capgo starts at $14/mo with Utilisation-based pricing that drops to roughly $0.001 per MAU. You also gain Chiffrement, automatic Restaurations, and worldwide latency monitoring.

Because AppFlow is now in maintenance mode, migrating sooner gives you access to ongoing Capgo innovation. We recommend switching when it fits your Libération schedule. Our engineering team will Aide you plan the changeover so your CI/CD and deployments keep running.

Capgo is engineered for enterprises that need Natif delta Mises à jour, Chiffré Bundles, and continuous innovation. Once you Migrer you can Supprimer the AppFlow glue code, rely on Natif automation, and keep shipping without interruption.