WhatsNew

Sign in

Accounts are created by the administrator.

WhatsNew store metadata, every language at once

Choose an app

Pick an App Store Connect key, load your apps, then select one. WhatsNew opens the version whose metadata is still editable (Prepare for Submission, rejected states).

No App Store Connect key yet — add one in Settings.

Languages on this version

Everything below is written per language. Add the ones you want here — no need to open App Store Connect. A new language is created on the version and on App Information, so the subtitle and privacy policy can be filled in too.

LanguageApp nameSubtitleWhat’s New DescriptionKeywordsApp info

Add languages

Apple needs a description and keywords on every language before a version can be submitted, so new languages start as a copy of an existing one. Translate them afterwards in the next steps.

Write the release notes once, then copy or translate them into every language. Limit 4000 characters.
Description, promotional text, keywords and support URL of the product page. Keywords are localized as ASO search terms rather than translated literally; the support URL is copied verbatim.

Only non-empty fields are pushed — a blank field never wipes what App Store Connect already has.

App name, subtitle and privacy policy URL live on App Information, which is app-level rather than per version —

With that box unticked the app name is left exactly as it is in every language — localizing only rewrites subtitles. Tick it and the brand is kept while the descriptive part around it is localized; review each one before pushing. Copy to all languages is the button that deliberately puts the same name everywhere.

The privacy policy URL is the same everywhere in most apps — “Copy to all languages” fills it in for every one; URLs are never translated. A language marked new has no App Information entry yet and is created on push; leave its name blank to inherit the current app name. Renaming an app goes through App Store review, and Apple rejects a name another app on the store already uses.

App Information could not be loaded for this app, so subtitle and privacy policy can’t be edited here.

Upload screenshots

Uploads go straight to this version’s languages in App Store Connect — there is no draft to commit. Upload order becomes display order.

Upload a whole folder — one subfolder per language

Example: shots/en-US/1.png · shots/tr/1.png. Folder names are matched against this version’s languages and everything is uploaded for the device size selected above. Untick any row you don’t want.

Open a listing

Loading a listing opens a draft edit against the Android Publisher API. Nothing reaches Google Play until you commit it in the last step; discarding the draft throws everything away.

No Google Play key yet — add one in Settings.

draft edit open

Languages in this listing

Languages added here exist only in the draft until you save the listings in step 2 — Google needs a title, short and full description for each one.

LanguageTitleShort descriptionFull description

Add languages

Pick from the ~85 languages Google Play supports. New languages start empty; translate them in step 2 and save.

Fill one language completely, then translate it into the rest. Play’s counterpart of the App Store subtitle is the short description. The privacy policy URL is a single app-level field the Android Publisher API does not expose — set it once in Play Console → App content.

Upload graphics

Save the listings first so newly added languages exist in the draft. Everything staged here is published by the commit in step 5.

Upload a whole folder — one subfolder per language

Example: shots/en-US/… · shots/tr-TR/…. Feature graphics (1024×500) and icons (512×512) are recognised by their pixel size, or by a file name like featureGraphic.png; everything else uploads as the image type selected above. Use the row filters to skip what is already uploaded.

Release notes belong to the release currently sitting on a track. Limit 500 characters per language.

Commit the draft

One commit publishes everything staged in this edit. Until then nothing you did in the steps above is visible on Google Play.

Staged in this draft

Nothing staged yet.

Push history

What this account pushed, when, and to which languages.

DateStoreAppWhatLanguages

App Store Connect keys

App Store Connect → Users and Access → Integrations → App Store Connect API → Team Keys → Generate API Key, role App Manager. The .p8 downloads once. Keys are stored AES-256-GCM encrypted and never sent back to the browser.

NameIssuer IDKey ID
Add a key

Google Play service accounts

Google Cloud Console → IAM → Service Accounts → Keys → JSON key. Then in Play Console → Users and permissions, invite the service account email with app access and the permissions Manage store presence and Manage production/testing releases.

NameService account
Add a service account key

Users

There is no self-signup — admins provision accounts. Deleting a user deletes their stored keys too.

EmailNameRole
Create a user