Documentation
Store listings
Edit the name, description, and screenshots shoppers see — then push text to Apple or Google.
Store listings is a peer of Overview. CapWrap is the editor. App Store Connect and Play Console remain the stores.
Draft vs live store
You write a draft in CapWrap. Refresh from store pulls live text when Apple or Google credentials exist. Save to App Store / Save to Play pushes text only. Screenshots stay in CapWrap for now — they are not uploaded to the stores yet.
A TestFlight upload does not change listing copy
The native pipeline skips metadata on purpose. Shipping a binary will not overwrite your App Store description. Listing save is a separate confirm.
iOS vs Android
Switch store at the top. Each store has its own fields and character limits (shown live). Copy a field from one store to the other when the idea is the same.
Apple: name, subtitle, promotional text, description, keywords, what’s new, plus support / marketing / privacy URLs and copyright.
Google: title, short description, full description, what’s new, website / support / privacy. Play has no keyword field — don’t invent one.
What’s new on Play is attached to a release. You need an Internal track release before some Play listing fields will stick.
Languages
Pick a main language (the one you write). Add more languages, then Translate. Translation runs on CapWrap’s servers. It fills empty fields and will not overwrite text you typed unless you confirm Replace. Translate is a draft — you still click Save to App Store / Play.
Screenshots
Upload PNG, JPEG, or WebP. Drag to reorder. You can reuse iOS shots on Android (and the reverse). Feature graphic is Play-only. Screenshot push to the stores is not available yet.
If a store is not connected
That column is read-only, with a link to Settings. You can still save a CapWrap draft.