Provider-facing SDK contracts for integrating custom Live Updates services with Ionic Portals and Federated Capacitor.
Ionic Appflow is being sunset, which impacts customers using Ionic Live Updates to deliver updated web assets to mobile apps.
Standard Capacitor apps can already integrate alternative Live Updates services without Ionic infrastructure changes. However, Portals and Federated Capacitor historically depended on Ionic/Appflow-specific behavior.
This SDK introduces a provider abstraction so Portals and Federated Capacitor can depend on a stable provider contract rather than provider-specific logic.
All providers implement manager sync behavior that fetches, stores, and activates web assets.
Provider responsibilities:
- Keep
latestAppDirectoryaccurate at all times - Ensure
latestAppDirectoryis correct when a manager is created - Update
latestAppDirectorybefore sync returns when new assets are downloaded - Clean up unused disk assets
To support Portals, implement manager contracts:
- iOS:
LiveUpdateManaging - Android:
LiveUpdateProviderManager
To support Federated Capacitor, implement provider + manager contracts:
- iOS:
LiveUpdateProviding+LiveUpdateManaging - Android:
LiveUpdateProvider+LiveUpdateProviderManager
Additional Federated Capacitor requirements:
- Package your provider as a Capacitor plugin
- Register your provider in
LiveUpdateProviderRegistryon plugin load - If you want sync metadata returned to JS, return
FederatedCapacitorSyncResult
- Source:
ios/Sources/LiveUpdateProvider - Package manager support:
- Swift Package Manager (
Package.swift) - CocoaPods (
LiveUpdateProvider.podspec)
- Swift Package Manager (
- Source:
android/live-update-provider - Maven coordinates:
io.ionic:liveupdateprovider:<version> - Android-specific setup and publishing details: android/README.md
ios/: iOS SDK source and testsandroid/: Android SDK source, tests, and publishing configscripts/: helper scripts (including Android publish helper)ionic-live-updates-architecture-customer.md: architecture guidance for teams building a service
As Appflow approaches sunset, teams that plan to build and operate their own Live Updates backend can use the architecture guidance document for implementation planning.
The document covers architecture, data requirements, security considerations, and operational responsibilities.
- Live Updates Service Architecture Overview:
ionic-live-updates-architecture-customer.md
Pre-1.0 releases may include API refinements as implementation feedback is incorporated.
See License.