Which Stacks Can Use Live Updates on Android? Capacitor, React Native, Flutter, Kotlin

Google Play allows live updates of interpreted code and bans downloading native code (dex, JAR, .so). Whether your app can ship over-the-air updates on Android depends on one question: is your app logic interpreted at runtime, or compiled to Android bytecode or machine code?

The policy behind this is explained in Does Google allow live updates?. This page applies it to each stack. For the iOS version, see which stacks can use live updates on iOS.

The rule in one sentence

Google Play’s Device and Network Abuse policy forbids downloading executable code from outside Google Play, except code that runs in a virtual machine or interpreter with indirect access to Android APIs, “such as JavaScript in a webview or browser”. That code must still follow every Play policy.

So: JavaScript and other interpreted code, yes. Kotlin, Java, dex, JAR and native libraries, no.

Android live update compatibility by stack

Stack by stack

Capacitor, Ionic and Cordova: fully covered

Your UI and business logic is JavaScript running in the Android WebView, the exact example Google’s policy gives for allowed code. A live update replaces the web bundle; the APK, native plugins and permissions stay the ones you published.

Capgo is compliant by design because it can only change the web layer. New native plugins, new permissions in AndroidManifest.xml and Gradle dependency changes still need a Google Play release.

React Native and Expo: JavaScript yes, native modules no

React Native runs a JavaScript bundle on Hermes, which counts as interpreted code. Expo Updates and the now retired Microsoft CodePush update that bundle. Teams leaving CodePush need a replacement. Native modules and React Native upgrades need a new release.

Flutter: only through a VM or interpreter

Flutter compiles Dart ahead of time into libapp.so. Downloading a new .so is explicitly banned, so stock Flutter cannot use live updates. Shorebird adds code push and states that it complies with Play policy by running updates through the Dart virtual machine. Read more in live updates for Flutter apps.

Native Kotlin, Java and Kotlin Multiplatform: no code updates

Loading downloaded dex or JAR files with DexClassLoader is the exact behavior the policy bans. Google’s own alternative is Play Feature Delivery, which downloads code modules through Google Play. Outside of that, you are limited to remote config, feature flags and server-driven UI.

Unity and game engines: content yes, code no

Game code is compiled. Asset bundles and Play Asset Delivery handle content, and embedded scripting languages like Lua are interpreted code, which the policy allows as long as the result follows Play policy.

Web wrappers and Trusted Web Activities: live by nature

A Trusted Web Activity or WebView wrapper loads your website, so it updates every time you deploy. Google Play accepts TWAs. You lose offline support and native plugins, which is where a bundled Capacitor app with live updates fits better.

What no stack can do on Android

Whatever your framework, a live update cannot:

• Download dex, JAR, APK or native .so files outside Google Play
• Add new Android permissions
• Make the app do something Google Play policy forbids
• Change the app into something the Play Store listing does not describe

Where to go next

• The policy: Does Google allow live updates?
• iOS version of this page: Which stacks can use live updates on iOS?
• Apple rules: Does Apple allow live updates?
• Compliance checklist: Checklist for Google Play OTA compliance

Ship live updates on Android with Capgo

If you build with Capacitor, Ionic or Cordova, Capgo live updates send your web changes to Android users in minutes, with channels, rollbacks, delta updates and end-to-end encryption.

bunx @capgo/cli@latest init

Follow the quickstart to send your first update.