App Store Connect Group Lab

Evangelists and engineers from the App Store Connect and App Review teams introduce themselves and set up the session, which covers the App Store Connect API and automation, TestFlight, app review preparation, subscriptions and retention messaging, the expanded App Store analytics, universal purchase, and getting an app discovered.

Build uploads, introduced last year, let you automate the whole develop-test loop end to end — upload a build, make it available to TestFlight testers, and pull tester feedback via the public feedback API to act on and upload again. The panel also called out combining the TestFlight feedback APIs with webhooks to auto-generate tickets in your own system, and the Power & Performance API for on-device storage and CPU reports, as underused.

Only you can judge which accessibility claims fit your app, so answer the nutrition-label questions as accurately as you can for what your app actually does. If a feature like captions doesn't apply because there's no audio, don't claim it — describe the real accessibility of the app so customers searching for it can find you.

Preparation is the key to a smooth review. Test on a real device the way your users will, exercise all functionality, resolve crashes, and verify in-app purchases work against production-ready systems. Use the app review notes to tell reviewers how to use the app, including any login or demo credentials, so they can evaluate it fully the first time.

Yes — you'll get rich data: how many people saw the retention message, how many clicked cancel, and how many stayed subscribed. You can A/B test different messages and offer alternate plans to see what resonates, using the analytics to measure what actually retains users.

Developers generally manage their keys well. The core guidance: don't hardcode API keys into your repository or ship them in clients, and manage your private key responsibly. If a key is compromised, revoke it in App Store Connect. Be especially careful with keys shared with third-party services — revoke a key when you stop using that service, scope its permissions tightly, and don't overshare information. The Users and Access APIs can also help you monitor who has access to your account against your own internal systems.

Yes. The auto-update-versus-manual breakdown is available in the downloadable analytics reports (not the dashboard) — look for the column that splits auto versus manual updates.

A general team key can't be scoped to specific apps. The alternative is an individual (user-based) API key, which inherits that user's access level in App Store Connect — so a user who can only see a couple of apps gets a key limited to those apps. That's the mechanism for narrowing an API key's reach today.

Name, subtitle, age rating, and genre are shared across all platforms of a universal-purchase app and can't differ per target — this consistency is intentional since the app can be downloaded across devices. The description, however, can be tailored per platform, so use it to reflect platform-specific functionality (and be mindful that differing privacy practices per platform need care).

Yes, localization is supported, and you should localize the retention message to match your app's localizations. A disjointed experience — where the app is translated but the retention prompt appears in English — feels jarring to users in other regions, so keep the language consistent.

Keep the user front of mind rather than stuffing in information — dense copy can be off-putting to someone evaluating whether to try your app. Tailor the message to your audience, and use custom product pages to route different audiences to different copy, or product page optimization to test variants.

Test within your own team first: add internal people as App Store Connect users and invite them to install and give feedback (ideal for distributing regular builds to QA). Once the app works as expected internally, move to external TestFlight, which goes through beta app review to keep content safe and trustworthy before reaching outside testers.

App Store Connect API keys belong on your server only — never embed them in a shipping app. Remember these keys don't expire, so treat them carefully. Apply least privilege: for team keys, choose the lowest role that gets the job done, and scope access with user-based keys where possible.

It hasn't changed — distinct bundle IDs still can't share an identical name, and unique names matter now that iPad apps run on Mac and apps span platforms. The recommended path is to add your Mac app to the iOS/Vision Pro app record and use universal purchase, which achieves a shared identity and brings additional benefits.

Thoroughly test the app and its third-party integrations, and make sure your keys and services are production-ready and can handle scale before submitting. If you're handling users' own API keys, demonstrate that you protect them in a privacy-friendly way on your side.

Use the StoreKit 2 AppTransaction API to read the original app version a customer purchased, so you can identify prior buyers and grant them the right entitlements. Then exercise the whole restoration flow in TestFlight with test accounts that hold different purchase histories to validate the behavior before shipping.

Lean on the developer website's tutorials, documentation, videos, and WWDC sessions — and don't limit yourself to this year's, since older sessions (going back years) remain relevant. The typical path is: create the app record, distribute through TestFlight, then submit to app review.

Invest in creative assets — plenty of screenshots and previews that clearly show what your app does. For organic discovery, use in-app events, and custom product pages tied to specific keywords to raise relevance. You can also submit a feature nomination to the editorial team, who may place a compelling app on the Today tab.

You don't need the full set — it depends on which platforms you distribute to and eligibility (e.g. Apple Silicon). Provide distinct metadata per platform and the binaries you actually target (such as an iOS binary, a macOS binary, watchOS). You can start with one platform and add others as you're ready.

English isn't required. App Review has broad language coverage and can often match a reviewer to your primary language, so you can write review notes in your native language. English may be a safe default, but it's optional — developers don't need to speak English to submit.

Look beyond the API at the web dashboard: over 100 new analytics metrics landed this year for subscription and in-app-purchase businesses, with visualizations you won't see through automation. Also note that Game Center entities like leaderboards can now be submitted alongside in-app purchases.

The most common causes trace back to not being fully prepared for review: bugs and crashes (test on-device as a real user, not just in Simulator), and incomplete information. Provide any demo credentials and highlight functionality in the review notes, and use TestFlight internal then external testing to refine the build before submitting.

Validation happens throughout the pipeline, and the teams continually work to surface feedback earlier. Pay attention to the warnings (not just errors) returned after upload — they list things to address before the next build. You can also validate your app in Xcode before delivery to catch issues locally.

Yes — use groups, available for both internal and external testing. A group defines which testers get which builds, so testers only see the builds assigned to their group. Organize by function (dev, QA, localization, power users) or set up a dedicated group for an in-progress feature so it stays separate from your regular build stream.

The delay exists so a price change can go live everywhere at the same moment. Because time zones differ around the world, the system needs time to propagate the change so it takes effect simultaneously across regions rather than at staggered local times.

Decide which app record you want to persist, then consolidate onto it — Apple did exactly this internally with Creator Studio, merging separate apps into one. Keep the listing you want to keep and bring the country-specific variations together under it rather than maintaining parallel submissions.

This spring brought the biggest App Store analytics update in over a decade — 100+ new metrics, mostly for in-app purchases and subscriptions. Data from App Store search, browse, and the Today tab now ties back to later purchases, so you can follow the full customer journey from download through purchase to renewal, with visualizations of conversion and retention rates.

Make your app genuinely interesting or novel — crowded categories are less likely to be nominated. Strong artwork helps you stand out; Apple released new assets you can place on your product page that also appear in featuring placements. A compelling app plus great art is the best path to being featured.

What counts as least-privileged depends on what the tool needs to do. For read-only, analytics-style needs the Sales role has the lowest level of access. The Developer role can upload builds and use internal TestFlight — a fit if you only need to upload and test. Neither the Developer nor the Marketer role can release an app or a new version; the Marketer role can change metadata, the product page, and app events. Choose the lowest role that covers what the key needs to do.

For sales and analytics data, the API updates on a daily cadence while the UI's Sales and Trends shows the last 24 hours — it's the same data at a different refresh rate. If you need the freshest numbers today, the UI is the place to get them; faster API data isn't currently available.

App Store Connect doesn't expose keyword-level data, but for a custom product page you can view its performance in App Analytics and filter by source type. Filter by App Store Search: with no Apple ads running, that reflects organic search; if you run ads it's blended, so consider two custom product pages — one for ads, one for organic — to separate the two.

Assuming a phased release, open the version page in App Store Connect and click into the phased release rollout to see which day of the rollout cycle you're on. Because you can have up to two versions per platform, you can check the phased-release state of the currently distributed version while working on the next one.

If reviewing the app requires being in a specific physical location, include a screen recording of the app in action with your submission so reviewers can evaluate the experience. Also design meaningful functionality for users who aren't at that location, since not everyone will be on-site.