Capacitor Performance

Find the bottleneck first (WebView JS, bridge, native, or network), then fix the specific cause. Generic web advice (code splitting, image compression, virtual lists) still applies; this skill focuses on what is different inside Capacitor.

When to Use

TRIGGER when:

• Cold start is slow, splash stays long, or the first screen is blank for seconds.
• App "restarts" or shows a white screen after taking a photo, opening a big file, or returning from background.
• Native calls feel slow, especially with images, files, or large HTTP responses.
• Scrolling/animations jank only on device (often older Android WebView).
• Memory grows over time; listeners pile up.

Do not use:

• Crashes, native stack traces -> debugging-capacitor, capacitor-native-observability.
• Getting logs off a device -> ios-android-logs.
• Offline storage design / SQLite migration -> capacitor-offline-first, sqlite-to-fast-sql.
• Splash screen setup -> capacitor-splash-screen; keyboard resize jank -> capacitor-keyboard.
• OTA bundle size and delta updates -> capgo-live-updates.