A Beginner’s Guide to App Store Connect

1. What exactly is App Store Connect?

App Store Connect is Apple’s management dashboard for developers and the teams running their apps. It manages the name, description, screenshots, price, and updates that users see on the App Store. It also gives you access to testing, review, sales, payments, and customer reviews.

2. What should you prepare before starting?

• An Apple Account with two-factor authentication enabled.
• An active Apple Developer Program membership, or an App Store Connect invitation from your team.
• A clear understanding of which team you are working with. If your account belongs to several teams, choose the correct one after signing in.
• An app name, primary language, Bundle ID, and internal SKU for creating the app record.
• A privacy policy URL, store description, keywords, screenshots, support URL, and review contact details before release.

Understand the roles first

A missing button often means you lack permission, rather than that the system is broken. Apple’s role documentation is detailed; this table is a useful starting point.

To invite a colleague, go to Users and Access → People → +, enter their name and email address, then assign a role and app access. Give people the access they need; do not make everyone an Admin simply for convenience.

3. Create your first app record before uploading a build

An app does not automatically appear in App Store Connect when someone uploads its binary. You must create an app record first, so developers can upload builds for it. Apple’s app creation instructions specify that order.

1. Sign in and open Apps.
2. Click + in the upper-left corner and choose New App.
3. Select a platform, such as iOS, macOS, tvOS, or visionOS.
4. Enter the Name, Primary Language, Bundle ID, and SKU.
5. Choose Full Access or Limited Access, then click Create.

What do these fields mean?

4. Complete the App Store listing

A newly created record usually starts in Prepare for Submission. You now need two kinds of information: details shared by the whole app, and details specific to the version you are releasing. Keeping those separate makes the process easier to follow.

Information shared across the app

Manage these details around General → App Information in the sidebar: the name, subtitle, category, age rating, Bundle ID, content rights, and related fields. The age rating is calculated from your answers to a questionnaire; answer accurately rather than choosing a rating by intuition.

App Privacy describes the data collected by your app and its third-party SDKs, whether that data is linked to users, and whether it is used for tracking. iOS apps need a privacy policy URL. Do not copy another app’s answers: Apple requires disclosures to reflect the actual data practices of both you and your third-party partners. Work through Manage app privacy item by item.

Information for each version

• Promotional Text: short promotional copy, such as information about a current campaign.
• Description: the full product description. Explain the problem the app solves before listing its main features.
• Keywords: terms that help people find the app. Avoid repeatedly stuffing in the app name.
• What’s New: what changed in this update. This is generally not needed for the first version.
• Support URL: a page where users can get help.
• Screenshots / App Previews: screenshots and optional preview videos for the relevant device sizes.

Screenshots are more than a few screen captures uploaded to a form. They are among the most important assets for App Store conversion. Lead with the core value, follow with use cases, and give each image one point to communicate. You can localize them for each language; Apple’s screenshot and preview instructions explain where to upload them.

Write review information for reviewers, not customers

App Review Information is for the review team only. Provide a contact who can respond promptly. If the app requires sign-in, supply a reliable demo account. If a feature requires a particular navigation path, piece of hardware, location, or action, describe the steps clearly. A reviewer who cannot find a feature may ask for clarification or reject the submission.

5. What is a build, and how do you test with TestFlight?

The version number is what customers see, such as 1.2.0. The build number identifies a particular packaged build internally, such as 37. You can upload several builds for one version, but select only one when submitting it for review.

Developers can upload builds with Xcode, Transporter, and other supported methods. A successful upload does not mean the build is immediately available: Apple needs to process it first. Once processing finishes, it appears under the app’s TestFlight tab.

Should you use internal or external testing?

1. Open the app’s TestFlight tab and complete the Beta App Description, feedback email, and testing instructions.
2. Create a test group and add the correct build.
3. For internal testing, add existing team users to the group. For external testing, submit for TestFlight review before inviting people by email or public link.
4. Ask testers to install Apple’s TestFlight app and accept the invitation.
5. Use TestFlight to review installations, Sessions, Crashes, and tester feedback.

6. Submit for App Store review and release

When testing is complete, return to the page for the version you intend to release. A build appearing in TestFlight does not mean it has been submitted to the App Store: TestFlight testing and App Store review are separate processes.

1. Complete all required fields on the version page and resolve any red error messages.
2. Select the final build in the Build section. Only one can be associated at a time.
3. Recheck privacy disclosures, export compliance, content rights, advertising identifiers, and review sign-in details.
4. Click Add for Review in the upper-right corner. This only adds the version to a draft submission.
5. Open Draft Submissions or App Review in the sidebar, check the items, and click Submit for Review. Only then does the submission enter the review queue.

These are the two buttons described in Apple’s app submission workflow. A common mistake is stopping at step 4: the app remains Ready for Review, making it look as though Apple is taking a long time to begin.

What do the common statuses mean?

7. How do you manage the app after launch?

Release a new version

On the app page, click + for the relevant platform to create a new version. Enter the new version number and What’s New, select the developer’s new build, and repeat the review submission process. Do not create a new app record for an update; that would create a different product.

Manage pricing and regions

Use Pricing and Availability to set the price, regions, and availability. Before making a free app paid or changing its regions, confirm that the agreements, tax information, and banking details are active. Consider the expectations of existing users and subscribers when changing prices.

Reply to customer reviews

Open Ratings and Reviews to see ratings and written reviews. Prioritize concrete problems such as crashes, sign-in failures, and payment issues. Do not publicly ask for private information such as email addresses or order numbers; direct customers to your support channel. After a fix, update your reply to let them know which version resolves the problem.

Manage in-app purchases and subscriptions

In-App Purchase and Subscriptions are the product systems inside your app, separate from the app’s own price. Each product needs a Product ID, display name, description, price, and review screenshot. Before launching subscriptions, understand subscription groups, renewal, grace periods, offers, and server notifications. Do not simply launch a test product as a production product.

Keep access and agreements up to date

Update Users and Access when colleagues leave or change roles. The Account Holder should also track membership renewal and new agreements in Business. Unsigned agreements can prevent app creation, paid features, or payments.

8. How do you read and understand app data?

Launch is only the beginning. App Store Connect has at least three distinct views of the data: Analytics follows users from discovery to usage, Sales and Trends shows sales performance, and Payments and Financial Reports shows final settlement. Their definitions differ, so do not expect their numbers for the same day to reconcile exactly.

Read Analytics as a funnel

Open Analytics, select your app, and choose a date range. For a beginner, this is a useful order:

Apple’s metric definitions explain that some App Store metrics become available only after at least five first-time downloads or pre-orders. Missing charts for a new app do not necessarily indicate a configuration problem; there may simply be too little data.

Look beyond totals: break the data down

• Source Type: Do users come from App Store Search, Browse, Web Referrer, or App Referrer?
• Territory: Which countries or regions bring downloads and revenue? Is localization working?
• Device / Platform Version: Are problems concentrated on a particular device or OS version?
• App Version: Did usage or stability change after the latest release?
• Campaign: Are tagged marketing links bringing in valuable users?

A simple routine is to review seven-day and 28-day periods against the previous period of the same length. Change one thing at a time: after updating screenshots, watch product page conversion; after improving the first-run experience, watch retention and Sessions. If you change five things in one day, it becomes difficult to tell which caused a change in the numbers.

Sales and Trends: understand sales performance

Use this section to track App Units, In-App Purchases, subscriptions, sales, and estimated proceeds, with filters for products, regions, devices, and other dimensions. It is closer to a business dashboard, but revenue is estimated and exchange rates and transaction states can still change.

Payments and Financial Reports: understand what you receive

This section is for financial reconciliation. Proceeds are the amount owed to the developer after applicable taxes and Apple’s commission are deducted from the customer price. The pages show payments, estimated proceeds, exchange rates, taxes, adjustments, and the last digits of the bank account. Apple explains that data for the previous fiscal month generally begins appearing on the first Wednesday of the current month, with regional reports generally ready by the first Friday. See View payments and proceeds for details.

9. A weekly checklist for beginners

• Check app status, App Review messages, and TestFlight feedback.
• Review impressions, product page views, downloads, and conversion over the last seven days against the previous seven days.
• Review retention, Sessions, crashes, and the distribution of major app versions.
• Check ratings and new reviews, and reply to users who need help.
• Look for unusual changes in in-app purchases, subscriptions, refunds, and proceeds.
• Record the week’s version, screenshot, pricing, and marketing changes so you can interpret the data.
• Each month, have finance download and archive the financial reports and reconcile actual payments.

10. Eight common problems beginners run into

11. A one-minute glossary