AppForShareCreate a free account

Your App Store and Google Play listings, in one editor

Pro and Team

App Store Connect and Play Console each have their own screens, sizes and character limits. When you ship in several languages, one listing change becomes a long afternoon. AppForShare puts both stores in one editor, with the limits counted as you type.

Everything goes through your own App Store Connect key and Google Play connection. Nothing is saved to a store until a person presses Save.

Example

App Store, English (U.S.)

  • Subtitle28 of 30
  • Keywords96 of 100
  • iPhone 6.9 inch6 screenshots
  • German, French, UrduAI drafts waiting for review
1 AI action per language translated.

Made for

  • Developers who keep listings in more than one language
  • Agencies that update store text and screenshots for clients
  • Teams that want a record of who changed which line and what it said before

What it ends

  • Counting characters by hand to fit a 30 character subtitle
  • Resizing screenshots until App Store Connect stops rejecting them
  • Translating a listing in a spreadsheet and pasting it into 12 languages
  • Not knowing what the description said before last week's edit

How it works

  1. Step 1

    Pick the app

    Apps from your App Store Connect and Google Play connections sit in one picker. Choose a language or add one.

  2. Step 2

    Edit with the limits shown

    App Store: name, subtitle, promotional text, description, keywords, what's new, URLs. Google Play: title, short and full description, video, contact details.

  3. Step 3

    Add screenshots and graphics

    Images are sorted into the sizes each store accepts and checked before upload. Reorder or delete them in place.

  4. Step 4

    Translate and review

    Pick the target languages and AI drafts each one, with keywords chosen for that language. You read and edit every draft before saving it.

Upload your store build to AppForShare once: testers get an install link, and the same file goes on to TestFlight or a Google Play track from the build page, with your own App Store Connect key or Google Play service account. Watch on YouTube

Every change kept

Each saved field keeps the text it replaced, with the person who changed it. "Put back" restores an older line in one click.

How each store treats a save

On the App Store, a version that is being prepared can change freely; on the live version only the promotional text can change, and it shows at once. Starting a new version copies the last version's text and screenshots, as Apple does.

Google Play has no draft listing: each save is sent to Google, reviewed by Google and then shown. That is why Play changes need an Admin of your workspace. AppForShare never cancels changes that are already in review.

Expo store.config.json in and out

Teams that keep App Store text in Git with Expo's EAS Metadata can import their store.config.json into the editor. The App Store fields fill in per language as unsaved changes, so you read them, add screenshots or translate them and save as usual. Export writes your App Store listing back as a store.config.json. Nothing is sent to Apple by the import itself.

What's New from your release defaults

Save the What's New text you reuse on every version, per language, in the release defaults of the app. "Fill What's New from defaults" puts it into each language the version has, and you save each one to Apple as usual. Google Play release notes defaults work the same way on the releases page.

Good to know

Questions

How much does translation cost?
One AI action per language. Pro includes 100 AI actions a month and Team 500, shared by the workspace.
Who can save changes?
Developers edit App Store versions that are being prepared. Live App Store promotional text and every Google Play change need an Admin, because they go public or to Google's review straight away.
Does it work without a store connection?
No. The editor uses your own App Store Connect key and Google Play connection, which you add on the Stores page.
Can I bring my EAS Metadata file?
Yes. Import store.config.json and its App Store fields become unsaved changes you review and save. Export writes the App Store listing back to the same format. Expo's format covers the App Store only, so Google Play text is edited here.

Read next

Try it on your own app

Free account in a minute. Pro starts with a 7 day free trial.

More features