What problem does it solve? Moving a Capacitor app off Capgo requires replacing the updater plugin, remapping configuration options and API methods, recreating channels, regenerating signing keys, and rewriting CI/CD pipelines — a process where subtle differences (app ID formats, timeout units, update strategies) easily cause broken updates or rollbacks. ## Core Features & Use Cases - Capgo Usage Detection: Scans package.json, capacitor.config, source imports, and CI/CD files to identify which Capgo features (Live Updates, CLI, code signing, native builds) are in use before migrating. - Guided Plugin and Config Migration: Replaces @capgo/capacitor-updater with @capawesome/capacitor-live-update matched to the Capacitor version, with a full option-by-option configuration mapping table. - API and CI/CD Translation: Maps every Capgo method, event, and CLI command to its Capawesome equivalent, including update strategy patterns (background, force update, manual sync) and pipeline authentication changes. - Use Case: A team with a Capacitor 8 app using Capgo live updates and GitHub Actions uploads can follow the steps to swap plugins, migrate channels and signing keys, and update their workflow to the Capawesome CLI with verification at each stage. ## Quick Start Migrate my Capacitor project from Capgo to Capawesome Cloud, starting by detecting which Capgo features my project currently uses.
