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
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
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.
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.
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.
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.
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
- AI translations are drafts. They are never saved without a person reading them, and they do not promise better ranking or more downloads.
- Google Play release notes per track and rollouts are on the Google Play releases page, not in this editor.
- Privacy labels, age rating and price stay in App Store Connect.
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
- Builds on GitHub Actions
- Flutter builds on GitHub Actions
- Flutter facts and checks
- Security scan on every build
- Connect Expo (EAS builds)
- Connect Codemagic
- Send store builds to TestFlight and Google Play
- TestFlight groups and beta review on send
- TestFlight feedback in your inbox
- iOS device registration
- Hands free device setup
- App Store submission
- Google Play releases
- TestFlight tester sync
- Tester app with notifications
- Tester groups and status
- Join links for testers
- Beta and Live channels
- Build history page
- Tasks and activity feed
- Feedback to Linear and Jira
- Release checklist, approvals and blockers
- Release page per version
- Install link controls
- Several links per build
- Retire a test build
- TestFlight and APK in one link
- Install page in 13 languages
- In-app update check
- .aab uploads
- MCP server for AI tools
- Tester feedback with screenshots
- In-app feedback link
- AI test plan for each build
- Diawi compatible upload API
- Remember my iPhone
- Install help and why it failed
- Email the install link
- Custom channel address
- Verified publisher
- Daily install email
- Zipped .app upload
- Manage link for guest uploads
- Test accounts on the install page
- Telegram notifications
- Permissions in plain words
- Reply to testers and star ratings
- Follow a channel by email
- Download button for a README
- Store pages
- Check a build before upload
- Token scopes and CLI tools
- Upload from Claude or ChatGPT
- Passkeys and email code sign in
- Free build tools
- How reports work
- Malware check on every upload
- AppForShare Android store
- Re-sign iOS builds
- Single sign on (SAML and OpenID Connect)
- Require two step sign in
- Send to Microsoft Intune
- Choose where build files are stored
- Mac and Windows builds
- Workspace address
- Automatic clean up of old builds
- Tester email from your own mail server
- Webex notifications