A complete app store listing brings together clear screenshots, accurate descriptions, relevant keywords and reviewed translations. Work through them in that order, then check exactly what is ready to send to each store.
If you already have captures and approved product details, a short session can produce a useful draft. Translation review, account setup and store approval need their own time. Use the six steps below as a preparation checklist.
1. Capture and design the screenshots
Capture the actual app on a device or simulator. Choose screens that show the main task, a useful result and any features people need to understand before installing.
Plan one explanation per image. “Review your weekly workouts” is clearer than “Unlock your potential.” Use sample data where necessary, but do not present fictional users, ratings or outcomes as customer evidence.
- Gather the captures and decide which one should appear first.
- Choose a layout in the screenshot generator.
- Replace the sample images and captions, then apply your colors.
- Export the sizes required by your app and inspect every file for clipping and sharpness.
Free-template save and export require an account. Pro collections and AI translation have separate access or token requirements. Device sizes and scaling rules differ by store; use Apple's specifications and Google's asset requirements before exporting.
For a closer look at screenshot order and testing, see the conversion guide.
2. Write the listing from an accurate brief
Write down what the app does, who it helps and what someone needs to use it. Include account requirements, paid features and supported languages. This brief gives you a reference for checking every sentence.
Metadata generation can prepare a first draft. Read it as an editor: remove invented features, replace generic phrases and check that each paragraph explains something useful.
| Field | App Store | Google Play |
|---|---|---|
| Name | 30 characters | 30 characters |
| Supporting short text | 30-character subtitle | 80-character short description |
| Description | 4,000 characters | 4,000 characters |
| Hidden keywords | 100-byte technical limit; validate the localized text | No separate field |
| Promotional text | 170 characters | No equivalent field |
These are limits, not targets. Keep a shorter draft when it says everything the reader needs. See the description guide for structure and examples.
3. Review the keyword choices
Start with phrases that describe the app's actual tasks. Check the results in your target store and country, then compare relevant alternatives. Autocomplete and tool scores can suggest terms to investigate; they do not reveal exact organic demand.
- On iOS: use relevant terms in the keyword field without repeating the name, subtitle or category. Do not add competitor names. Check Apple's character and byte guidance for localized text.
- On Google Play: use task language naturally in the title and descriptions. There is no useful fixed repetition target.
- On both: prefer a clear sentence to an awkward combination of keywords. Save the chosen terms and market so later checks are comparable.
The keyword research guide explains how to turn those observations into a small list you can maintain.
4. Translate the markets you can support
Choose a market from existing users, customer requests or other evidence relevant to your app. Check that the service, purchases, login and support work there before translating the listing.
Use AppDrift's translation workflow to prepare selected drafts. Review the token quote, provide any approved terminology, and ask a fluent speaker to check the result.
- Does the text mean the same thing as the source?
- Does it use natural local words for the task?
- Do the captions fit the layout and match the interface shown?
- Are the app's supported languages and access requirements clear?
Give every published language a review. Expanding the list also adds future screenshot, product and support work; AI generation does not remove that maintenance.
5. Check the complete listing
Review the text and images together. A caption may promise something the description qualifies, or a new capture may show a feature that has not shipped yet.
- Validate each final field in the destination store.
- Open exported screenshots and confirm device size, crop, reading order and contrast.
- Remove placeholders and unsupported claims about rankings, awards or customer results.
- Check support and privacy links.
- Confirm the selected app, locale and version before sending.
- Save the approved text and assets so you can identify what changed.
Automated checks can catch length and file problems. They cannot decide whether every product claim is accurate or guarantee store approval.
6. Send the reviewed work and verify its status
AppDrift can send supported listing text through connected store accounts on eligible paid plans. Supported Apple screenshot uploads go to an App Store Connect draft after setup; export Google Play screenshots for manual upload.
Use Listing updates to compare the prepared version with the current copy. Check the fields and locales you intend to send, complete the supported action, and inspect its result.
A saved draft, a successful upload, a review submission and a public listing are different states. Binary building, signing, upload and store approval remain part of your release process. See the publishing guide for the broader workflow.
After launch, check the experience first
Open the public listing in the intended market and install the released app. Confirm that the images and copy match the product and that a new user can complete the main task.
Then review downloads, store conversion, selected keywords and customer feedback over comparable periods. A missing rank after two days does not identify a bad keyword strategy; data may be sparse or delayed. Look at the source and market before drawing a conclusion.
Investigate crashes, failed sign-in and surprise payment requirements promptly. For listing experiments, give the test enough eligible traffic and preserve inconclusive results.
Save the work for the next release
Keep the screenshot project, approved wording and publication dates together. Update the listing when features or requirements change, and revisit research when a specific question needs answering.
The AppDrift platform brings these preparation tasks together. Use the ASO checklist to track the remaining work. Free includes 50 AI tokens once; paid plans and token packs add capacity according to their current limits.
FAQ
Can I complete a listing in 30 minutes?
You may prepare a useful draft if your assets and product details are ready. A finished multilingual listing also needs language review, store validation and approval, which do not fit a guaranteed deadline.
Do I need separate listings for App Store and Google Play?
Adapt the same product explanation to each store's fields and asset requirements. Apple has a subtitle and hidden keyword field; Google Play has a short description and no equivalent hidden field.
How many screenshots should I prepare?
Use enough distinct images to explain the app and meet the requirements for its supported devices. Check the current store specifications rather than filling every slot with repetitive screens.
What should I check in the first 48 hours?
Confirm public availability, listing accuracy and the released app's main task. Investigate failures and collect early analytics, allowing for reporting delays and small samples.
Should I translate before launch?
Translate the markets you can support and review properly. Start with a manageable set justified by your audience; there is no universal language list for every app.
