Update your Google Play listing without a new release
You want to swap out screenshots, fix a typo in the description, or drop in a new feature graphic on Google Play. You do not want to cut a new build, bump the version code, and run a rollout just to do it. On Play you do not have to. The listing and the release are two separate objects, and Play Console lets you touch one without the other.
Google Play splits the listing from the release
Two things live side by side in Play Console. The app is your APK or AAB releases —
versioned binaries you roll out through tracks. The store listing is everything a
user sees on the store page: app name, short and full description, screenshots, feature graphic, and
icon. You edit the listing under Grow users → Store presence → Main store listing, and
those edits are independent of any release.
There is one requirement: the app has to have been published at least once. The listing first goes live alongside your first release. After that, you can edit it on its own for the rest of the app's life. Changing the description with no bundle change is a normal, supported flow — you edit the field, save, and submit the listing change by itself.
How to publish a listing-only change
- Open the listing. Play Console → your app →
Grow users → Store presence → Main store listing. - Edit what you need. Replace screenshots, update the feature graphic, rewrite the short or full description, adjust the name or icon.
- Save and submit the change. No release is attached. Play Console tracks it as a store listing change, distinct from an app bundle update.
- Let it publish. With managed publishing off, approved changes go live automatically once review clears.
What goes live fast, and what gets reviewed
Not every field behaves the same. Screenshots and most text changes usually appear on the live store page within a few hours. But some elements — the app name and the icon in particular — are subject to Google's review, and that can run from a few hours up to a day or two before the change shows publicly.
- Fast: screenshots, feature graphic, and most description edits typically go live within a few hours.
- Reviewed: app name, icon, and certain other elements may be checked by Google and can take up to a couple of days.
The practical takeaway: if a listing refresh has to line up with a launch date or an ad campaign, submit the name and icon changes a day or two early rather than the morning of. Screenshots you can usually leave later.
Managed publishing holds approved changes until you say go
If you want tighter timing, turn on managed publishing from the Publishing overview. With it enabled, store listing changes — including custom store listings and store listing experiments — are held after they clear review. They sit in a "changes ready to publish" state, and nothing goes live until you click publish yourself.
That is what you use to coordinate a listing update with a launch event, a press hit, or a paid campaign: get everything approved ahead of time, then release it all at the exact moment you want, instead of watching each change trickle out whenever review happens to finish.
Apple does the opposite — and that is the catch
This is where teams shipping to both stores get caught. On the App Store, your default screenshots are tied to an app version. To change the screenshots on a live app, you create a new version and send it through App Review — even if the binary itself does not change. There are narrower paths around it (custom product pages and Product Page Optimization tests), but the default listing follows the version.
So the identical task — "just change the screenshots" — is a lightweight listing edit on Google Play and a version submission on Apple. If you manage both, keep that asymmetry in mind: a quick Play listing tweak is genuinely quick, but the same tweak on the App Store means queuing behind App Review.
Where Mokbi fits
Mokbi handles the whole listing. Design your screenshots and feature graphic, draft the full listing text, and translate the entire thing into 50 languages so every locale's store page reads like it was written by a native speaker rather than run through a machine.
Then Mokbi publishes it for you. For Google Play it pushes the listing text and assets straight to the store through the Play Developer API — no new build, no manual copy-paste into Play Console. For the App Store it stages everything in App Store Connect ready to submit; Apple requires you to press Submit and clear App Review yourself, which is an Apple rule, not a limitation of the tool. Either way, the assets and copy land in every language and the listing goes out the door.