Overview / Guide
Migrate an existing app
Move to the current setup while keeping your application’s responsibilities clear.
Use standard setup as the target, then follow the migration guide for the packages already installed. Check the theme and plugin guides together when your application uses both.
Application state, routing and event handlers remain in the application. Ordinary startup belongs at the app shell; introduce custom lifecycle management only when your application actually replaces that shell. iOS 26 documentation remains available for existing users.
Keep app behavior, replace integration wiring
Keep routes, state and event handlers. If an earlier guide introduced a mountNativeUI wrapper solely for ordinary startup, remove that wrapper and its teardown wiring. Start once at the app shell and keep the default controls. For device layout, replace direct placement mapping with the resolver in the existing layout subscription rather than adding a second listener.
Verify the complete result
After updating compatible packages, build the Web assets, sync Capacitor and rebuild the native applications. Check ordinary phone layout and supported rail devices, existing actions and routes, both appearance modes and color fallback. Cordova bundles its integration through its own plugin release; follow that package’s instructions instead of applying the Capacitor commands.