OtaKitDoes Google allow live updates without Play review?
The direct answer for Android: yes, for interpreted web-layer code. What Google Play's Device and Network Abuse policy actually restricts, and how Capacitor OTA updates stay inside it.
Short answer: yes — Google Play allows over-the-air updates to your web-layer code. Android developers ask this less often than iOS developers, because Google's policy has always been more permissive here, but it's worth knowing exactly what the policy restricts so you stay comfortably inside it. Here's the direct answer for Capacitor apps.
The relevant policy is Google Play's Device and Network Abuse policy. It restricts downloading executable code (like dex or native code) from outside Google Play — not interpreted web content.
What the policy restricts
The Device and Network Abuse policy prohibits apps from introducing or exploiting the download of executable code (such as dex, JAR, or .so files) from a source other than Google Play, in a way that changes the app's behavior. The intent is to stop apps from sideloading native payloads that dodge review and could be malicious. It is not aimed at your JavaScript.
Why Capacitor OTA is inside the policy
- Capacitor updates ship interpreted web assets — JS, HTML, CSS — not dex or native binaries.
- They run in the WebView, the same as any web content your app already loads.
- They don't alter the app's native code or dodge Play's security model.
That's the same distinction Apple draws with guideline 2.5.2 — interpreted vs native. See the full checklist in the Google Play OTA compliance checklist.
Staying compliant
Keep updates to the web layer, don't use them to change the app's core purpose, and don't ship anything you couldn't have submitted through Play in the first place. Do that and OTA updates raise no policy concern. See app-store-compliant OTA updates.
As with iOS, the failure mode is intent: using updates to smuggle in behavior review would have rejected. Ship the honest version of your app faster — that's the whole point — and there's nothing to worry about.
Where to go next
See the Apple answer and updating without repeat review for the practical workflow on both platforms.