Skip to main content

App Store Listing Checklist: Screenshots, Metadata and Privacy Labels

By the OnlineAppCreator editorial team4 min read

Short answer

A complete store listing needs a name, subtitle or short description, full description, keywords on iOS, correctly sized screenshots from the real app, an icon, a privacy policy URL, a support URL and accurate privacy disclosures: Apple's App Privacy labels and privacy manifests, and Google's Data safety form. Prepare these in parallel with development so they do not delay your launch.

On this page
  1. Apple App Store: text fields and limits
  2. Google Play: text fields and graphics
  3. Screenshots that pass review and convert
  4. Privacy disclosures: labels, manifests and Data safety
  5. Review information and account access
  6. Localization and maintenance

The store listing is the first thing reviewers check and the first thing potential users see. For apps built with AI tools, it is also where launches are often delayed, because nobody prepared the texts, the screenshots or the privacy answers until the build was ready. This checklist covers what both stores require, the limits that trip people up and how to write a listing that helps both review and conversion. Limits and required sizes change from time to time, so confirm the current values in App Store Connect and the Play Console before you produce final assets.

Apple App Store: text fields and limits

At the time of writing, the App Store listing includes the app name (up to 30 characters), a subtitle (up to 30 characters), a keywords field (up to 100 bytes, comma-separated, not visible to users), promotional text (up to 170 characters, editable without a new submission) and the description (up to 4000 characters). You also need a support URL, a privacy policy URL, a category, an age rating questionnaire and a copyright line.

Use the name for your brand plus, if space allows, the core function. Put the main benefit in the subtitle. In the keywords field, do not repeat words already in the name or subtitle, avoid spaces after commas, skip competitor brand names and use singular forms where possible. Write the description for people, not algorithms: first sentence states what the app does and for whom, followed by short paragraphs on the main tasks.

Google Play: text fields and graphics

Google Play currently uses an app name of up to 30 characters, a short description of up to 80 characters and a full description of up to 4000 characters. Google indexes the full description for search, so naturally include the terms users search for, without keyword stuffing, which violates policy. Graphics include a 512 x 512 pixel icon, a 1024 x 500 pixel feature graphic and at least two phone screenshots; tablet screenshots are recommended if the app supports tablets. Avoid claims like "best" or "number one" and calls to action such as "download now" in the title or graphics, which Google's metadata policy restricts.

Screenshots that pass review and convert

Apple currently requires screenshots for the largest iPhone display size, which it uses to scale for smaller devices, and for iPad if your app runs on iPad. You can upload up to ten per localization. Check App Store Connect for the exact pixel dimensions accepted at the time of your submission.

For both stores, screenshots must show the real app in use. Marketing frames, short captions and device mockups are fine as long as the interface is visible and accurate. For AI-built apps, populate the app with realistic sample data before capturing, hide debug elements and make sure every screen shown actually exists in the submitted build. Lead with the screen that best explains the value, since many users never swipe past the first two. App preview videos on iOS are optional and must consist of footage captured from the app.

Privacy disclosures: labels, manifests and Data safety

Apple's App Privacy section, often called nutrition labels, asks which data types your app collects, whether they are linked to the user's identity and whether they are used for tracking. Apple also requires privacy manifest files that declare data use and certain API usage reasons for your app and for third-party SDKs included in it. Google's Data safety form asks similar questions about collection, sharing, encryption in transit and deletion options.

  1. List every service the app talks to: backend, authentication, analytics, crash reporting, push provider, payment provider and embedded third-party scripts.
  2. For each, note which data types it receives, such as email, name, user IDs, device IDs, location, content or usage data.
  3. Decide for each data type whether it is linked to the user and whether it is used for tracking or advertising.
  4. Answer Apple's App Privacy questions and Google's Data safety form from this inventory, not from memory.
  5. Make sure your privacy policy names the same processors and purposes.
  6. Confirm that your native shell and SDKs include current privacy manifests.
  7. Repeat the inventory whenever you add a service, including features added later through your AI builder.

Inconsistencies between these disclosures and the app's behavior are a common reason for rejections and later policy notices, which we cover in top rejection reasons for AI-built apps.

Review information and account access

Both stores ask how reviewers can access the app. Provide a demo account with realistic data, not an empty account, and test the credentials on a fresh install the day you submit. In Apple's review notes, describe the purpose of the app, the audience, where to find key features and native capabilities, and any special setup. On Google Play, fill in the App access section with the same credentials and instructions. If the app is a web-based app, stating its native features explicitly helps with Guideline 4.2.

Localization and maintenance

If you target several countries, localize at least the name, subtitle or short description and screenshot captions for your main markets. Keep a single source document with all texts, limits and the date of each change, so that iOS and Android listings stay consistent and updates are quick. For new personal Google Play accounts, remember that production access currently requires a closed test first, as explained in our closed testing guide.

If you would rather hand over the listing, screenshots, privacy forms and reviewer communication, AppSubmitter handles the whole publishing process for the App Store and Google Play until your app is live. A polished listing is also a product asset: when we build and launch digital products as a company builder, the store presence is planned alongside the product, not after it.

Frequently asked questions

How many screenshots do I need for the App Store?

You need at least one for each required display size and can upload up to ten per localization. In practice, five to eight well-chosen screenshots work well.

Can I change App Store text without a new build?

Promotional text can be changed at any time. Most other fields, such as the description and keywords, are updated together with a new app version submission.

Where do I find what my SDKs collect?

SDK providers publish data collection details in their documentation and privacy manifests. Combine those with your own backend's data to complete Apple's labels and Google's Data safety form.

Are mockups allowed in screenshots?

Yes, device frames and captions are allowed as long as the screenshots show the actual app interface and do not misrepresent its features.

Want this done right, the first time?

OnlineAppCreator takes products from idea to operation. Tell us where you stand and get a concrete plan in a free 15-minute call.