App Store & Play

# Google Play In-App Updates: Ship the Patch Without a Store Lottery

In-app updates on Google Play are a release tool: flexible or immediate, inside your Console, after a build that already passes review.

CodeLoop Studio·August 27, 2026·5 min read

![Person using an Android phone](https://www.codeloop.ba/_next/image?url=%2Fblog%2Fgoogle-in-app-updates-cover.jpg&w=3840&q=75)

Photo by [Lisa Fotios](https://www.pexels.com/@fotios-photos) on [Pexels](https://www.pexels.com/photo/1092644/)

Google Play in-app updates are a release tool: the app can prompt for a flexible download or block until an immediate patch installs. They are not a substitute for a listing that already passes review, and they are not an iOS feature with a different name.

CodeLoop Studio in Sarajevo ships Android in Kotlin. You keep the Play Console. How we get a build to the store is [shipping from Sarajevo](https://www.codeloop.ba/blog/shipping-app-store-from-sarajevo). New screens are [Jetpack Compose](https://www.codeloop.ba/blog/android-compose-ui). This page is when we wire Play Core updates, and when we will not.

## Flexible versus immediate

Flexible updates download in the background while someone still uses the app. Immediate updates are for something that must not keep running: a broken payment path, a crash loop, a policy fix. Most product increments are flexible. Treating every version as immediate is how you train people to force-quit.

[Koliko](https://www.codeloop.ba/study-case/koliko) is inventory on a shift — a mid-count is a bad moment for a blocking update. [WoodMeter](https://www.codeloop.ba/study-case/woodmeter) is field measurement; the patch has to respect the job, not the release calendar we find convenient.

## What we freeze

* **Your Console.** Signing, data safety, staged rollout. We work in your org. We do not “hold the keystore for safekeeping.”
* **A version that already passed review.** In-app updates cannot rescue a build Google has not accepted. Review notes sit in the plan for [custom mobile app development](https://www.codeloop.ba/custom-mobile-app-development).
* **Device QA.** Cheap Androids, not only a Pixel on Wi-Fi. Play Core failing on API levels you still support is a product bug.
* **No last-Friday bolt-on.** We will not add in-app updates the night before launch because a competitor blog mentioned them. Native versus cross-platform is still a stack decision — [native iOS and Android](https://www.codeloop.ba/blog/native-ios-android-app-development).

## iOS is a different store

App Store has no Play-style in-app update API. Phased release and TestFlight are the levers. Mixing the two in one sentence is how briefs go wrong. Dates and zones on iPhone are [iOS dates and timezones](https://www.codeloop.ba/blog/ios-dates-and-timezones).

## Send the Console, not a screenshot of a toast

Package name, whether you already ship staged rollouts, and what must never interrupt a shift. Reply in **24 hours** — [online estimate](https://www.codeloop.ba/online-estimate) or [contact](https://www.codeloop.ba/contact).