Capacitor live updates FAQ
The questions developers actually ask about Capacitor live updates — are they allowed, what can you ship, how fast, how safe, how much they cost — answered in one place with links to the details.
These are the questions developers actually ask before adopting Capacitor live updates — answered directly, with links to the full details. If you're evaluating over-the-air updates for a Capacitor app, start here.
Are live updates allowed by Apple and Google?
Yes, within limits. Apple's guideline 2.5.2 permits updating interpreted code (your JavaScript) as long as you don't change the app's core purpose or download native executable code. Google Play similarly allows web-layer updates. See does Apple allow live updates, does Google allow live updates, and guideline 2.5.2 explained.
What can I ship over the air, and what can't I?
You can ship anything in the web layer: JS, CSS, HTML, assets, most business logic and UI. You cannot ship native code changes — new plugins, permissions, or SDK bumps still need a store build. See app-store-compliant OTA updates.
How fast do updates reach users?
A bundle is available the moment you release it. Devices pick it up on their next check (typically next launch), and you can force an immediate apply for urgent fixes. See deploy a hotfix in minutes and update UX options.
What if an update is broken?
If a new bundle fails to boot (never calls notifyAppReady()), the device automatically rolls back to the last known-good bundle. You can also roll the channel forward to a fixed build. See rollback strategies.
Is it secure?
Bundles are signed and verified against a SHA-256 manifest before activation, and can be end-to-end encrypted. A device won't run a bundle that doesn't match what your signing key vouched for. See OTA update security.
Can I roll out gradually or to specific users?
Yes. Use staged rollouts to ramp a release, and channels to target beta groups or tenants. See staged rollouts and targeting users.
How much does it cost?
With OtaKit, there's no MAU or bandwidth metering — most apps pay $0–25/mo. That differs sharply from tools that meter monthly active users. See the pricing comparison.
Do updates work offline?
The device keeps its current bundle and simply checks for updates when it next has a connection. A failed or missing check never breaks the installed app. See offline support.
Can I self-host?
Yes — OtaKit is fully MIT-licensed and self-hostable, with static-CDN delivery that makes self-hosting practical. See self-hosted live updates.
Still deciding whether Capacitor + OTA is the right stack at all? Read React Native vs Capacitor and how OTA works.
Where to go next
Ready to try it? Start with Setup. Want the operational playbook first? See the update strategy checklist.