All posts

App Store product page for a first app: pre-submit check

· 7 min read

Your App Store product page is the first thing a stranger sees. In App Store Connect it is a set of text fields, screenshots, an optional video, privacy answers and an age rating. Apple checks all of it at review. This post goes through each part, quotes the limits and the rules, and ends with a checklist for your first submit. I read Apple's pages on 10 November 2026. Limits change, so check the linked pages again before you rely on them.

The text fields and their limits

Apple's App information page and its Platform version information page give these limits:

  • App name: "at least two characters and no more than 30 characters".
  • Subtitle: "can't be longer than 30 characters". It appears under the app name on your product page.
  • Promotional text: "can't be longer than 170 characters".
  • Description: "Limited to 4000 characters." Apple says it should be plain text and HTML is not supported.
  • Keywords: each keyword must be "greater than two characters", and you get "up to 100 bytes of content". Apple adds that "Names of other apps or companies aren't allowed."
  • What's New in this Version: "Limited to 4000 characters." It is not available for the first version, but it is required for every later one.

One more thing about promotional text. Apple says it lets you tell visitors about current app features "without requiring an updated submission". That is the only field the page names as changeable without a new submission. For the other fields, check Apple's "Required, localizable, and editable properties" page before you plan a change.

Screenshots

Apple's Screenshot specifications page sets what you must upload:

  • iPhone: "At least one screenshot for iPhone with Dynamic Island (medium display)." Accepted sizes are 1179 x 2556 or 1206 x 2622 pixels in portrait, or 2556 x 1179 or 2622 x 1206 in landscape.
  • iPad, if your app supports iPadOS: "At least one screenshot for iPad 13-inch display." Accepted sizes are 2064 x 2752 or 2048 x 2732 in portrait, or 2752 x 2064 or 2732 x 2048 in landscape.
  • Count: "You must include at least one screenshot", and you can upload "up to 10 screenshots per device size".
  • Format: ".jpeg, .jpg, or .png". Images "can't include alpha channels or transparencies".

Mac, Apple TV, Apple Vision Pro and Apple Watch apps have their own required sizes on the same page. It also says all screenshots must follow the App Review Guidelines before you submit.

App previews (video)

Previews are optional. Apple's App preview specifications page says:

  • "You can upload up to three app previews per supported device size and language".
  • Length: minimum 15 seconds, maximum 30 seconds. Maximum file size: 500MB.
  • Formats: ".mov, .m4v, .mp4 (H.264)", or ".mov for ProRes 422 (HQ only)".
  • iOS previews can be landscape or portrait.
  • Previews appear before screenshots on iPhone and iPad.

The page lists exact accepted resolutions for each device size, and says to upload at the accepted resolution, not the device resolution. It also says processing can take up to 24 hours after upload, so do not add a video at the last minute.

App Privacy details

Apple's App privacy details page says you must "identify all of the data you or your third-party partners collect", unless the data meets every criterion for optional disclosure. These answers are what shows as the privacy "nutrition label" on your page.

  • Third-party code counts. Apple defines third-party partners as "analytics tools, advertising networks, third-party SDKs, or other external vendors whose code you've added to your app". If an SDK collects data, you disclose it.
  • The reason does not matter. "Even if you collect the data for reasons other than analytics or advertising, it still needs to be declared."
  • What "collect" means. Transmitting data off the device so you or your partners can access it for longer than needed to serve the request in real time. Data processed only on the device "is not 'collected'".
  • Privacy policy link. Marked "Required". The Privacy Choices link is optional.
  • Keep it current. "You're responsible for keeping your responses accurate and up to date." You can update the answers at any time without an app update.
  • Data from Apple. "You are not responsible for disclosing data collected by Apple."

The page lists 16 data type categories, such as Contact Info, Location, Identifiers, Usage Data and Diagnostics. It also covers tracking and whether data is linked to the user. Go through your SDK list one by one before you answer. For the Google version of this form, see the Data safety form post.

The age rating questionnaire

Apple's Age ratings page says you specify "the frequency or presence of each" item, and "Apple generates appropriate ratings based on your answer". The questions cover groups such as in-app controls, capabilities (for example user-generated content, messaging and chat, advertising, unrestricted web access), mature themes, sexuality or nudity, violence and chance-based activities. Rating values are 4+, 9+, 13+, 16+ and 18+. An unrated app "can't be published on the App Store". Answer honestly. Guideline 2.3.6 says a mis-rated app can surprise customers or "trigger an inquiry from government regulators".

What App Review says about metadata

The App Review Guidelines cover this in section 2.3, Accurate Metadata. The parts that matter most for a first app:

  • 2.3: metadata, "including privacy information, your app description, screenshots, and previews", must "accurately reflect the app's core experience".
  • 2.3.1: "promoting a false price" or promoting services the app does not offer is grounds for removal. Notes for Review must describe new features "with specificity" and "generic descriptions will be rejected".
  • 2.3.2: if you have in-app purchases, your description, screenshots and previews must "clearly indicate" whether featured items need additional purchases. Test them first: see testing in-app purchases.
  • 2.3.3: "Screenshots should show the app in use, and not merely the title art, login page, or splash screen."
  • 2.3.4: previews "may only use video screen captures of the app itself".
  • 2.3.6: answer the age rating questions honestly.
  • 2.3.7: "don't try to pack any of your metadata with trademarked terms, popular app names, pricing information, or other irrelevant phrases just to game the system". Names are limited to 30 characters. Subtitles "should not ... reference other apps, or make unverifiable product claims".
  • 2.3.8: icons, screenshots and previews must fit a 4+ rating, even if your app is rated higher. "For Kids" and "For Children" are reserved for the Kids Category.
  • 2.3.9: you must hold the rights to all materials, and "display fictional account information instead of data from a real person".
  • 2.3.10: "don't include names, icons, or imagery of other mobile platforms or alternative app marketplaces". Keep metadata focused on the app itself.
  • 2.3.12: new features go in the "What's New" text. Simple bug fixes may use a generic description.

For what happens when one of these goes wrong, read the post on common first rejections.

A check to run before you submit

  1. Name and subtitle. Each is 30 characters or less. No competitor names, no prices, no claims you cannot prove.
  2. Keywords. Within 100 bytes. No other apps or companies. Nothing that is not about your app.
  3. Description. Plain text, under 4000 characters. Every sentence is true for the build you are submitting.
  4. Promotional text. Within 170 characters. Treat it as the line you can change later.
  5. Screenshots show the app in use. Not only a splash screen or login page (2.3.3).
  6. Screenshot sizes. At least one for the required iPhone size, and one for iPad 13-inch if you support iPad. PNG or JPEG, no alpha.
  7. No other platforms. No Android logos, no other store badges, in screenshots, previews or text (2.3.10).
  8. Fictional data only. No real names, emails or photos in screenshots (2.3.9).
  9. Privacy answers match the code. Go through every SDK. Add the privacy policy link and open it on a phone.
  10. Age rating answered honestly. Check it against what your app really shows.
  11. Notes for Review. Say what the app does, and include a working demo login if the app needs one.
  12. Test the build first. Run it on a real phone before you submit. See the TestFlight public link post.

Compare with Google Play

If you ship on both stores, the fields and rules are close but not the same. Limits and image rules differ. I wrote the Android side up in the Google Play listing post.

Where TestSwap fits

TestSwap is a free site where app makers review each other's apps. It is not affiliated with Apple. A tester can't approve your product page. But a stranger can tell you what they think your app does from the screenshots and the first screen alone. If that answer does not match your description, fix the page before Apple or a customer finds the gap.

  • Makers post web, iOS and Android apps with a link testers can open or install, like a TestFlight link.
  • You can add a test login that only signed-in testers see.
  • Everyone starts with 3 credits. Writing a review earns 1, and each review your app receives costs 1.
  • The maker can rate each review 👍 or 👎, and a 👎 takes back the reviewer's credit.

Give testers one clear job, for example "look at the screenshots and the first screen, write one sentence on what you think the app does, then use it for 10 minutes and tell me what did not match". I wrote about that in how to write a test task.

Try it

Post your app on TestSwap with a task that sends testers to your screenshots and first screen before anything else. Reviewing someone else's app first is the quickest way to see how it works. Tell me what's missing or broken (@dizid on X).