---
title: "App Store Connect | Skills We Assign For | Azendo"
description: "App Store Connect in the release path — review timing, metadata and what to plan around, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/app-store-connect/"
---

[Skills](https://azendo.co/skills/) CI and delivery 

# App Store Connect.

App Store Connect is Apple's portal for managing applications: builds, metadata, pricing, in-app purchases, review submission, tester management and the analytics Apple reports. Every iOS release passes through it.

## Where App Store Connect fits on a long engagement.

Review is an external dependency on the roadmap, and treating it as one changes planning. Most reviews complete within a day, but rejections happen for reasons that are not always predictable in advance, and a rejection late in a release window can move a date the business had committed to.

Phased release is the feature most worth using and most often ignored. Rolling a version out to a percentage of users over several days means a defect that escaped testing affects a fraction of the installed base rather than all of it, and the release can be halted.

## What an assigned team does with App Store Connect.

Store metadata is a marketing asset, not a technical one. Screenshots, description and keywords affect conversion from store listing to install, and they are routinely written once at launch and never revisited while the product changes around them.

Keeping that current alongside the product is a continuity outcome rather than a launch task, and it is the sort of thing a standing assignment holds, as described in [how an assignment runs](https://azendo.co/how-it-works/).

## What we use App Store Connect for.

* Planning around review as a dependency Submission windows built into the roadmap rather than assumed to be instant.
* Phased rollout as standard Releases staged across days, so an escaped defect reaches a fraction of users.
* Listing kept current with the product Screenshots and copy revisited as features change, because they drive install conversion.

## How App Store Connect capacity is assigned.

Store operations are part of the release path a mobile assignment owns, rather than a separate responsibility handed back at submission.

## Roles we assign App Store Connect for

* [iOS Developer Mobile development](https://azendo.co/services/mobile-development/ios-developer/)

## Service lines it sits in

* [Mobile development](https://azendo.co/services/mobile-development/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in ci and delivery

* [GitHub Actions — skill we assign for](https://azendo.co/skills/github-actions/)
* [Jenkins — skill we assign for](https://azendo.co/skills/jenkins/)
* [GitLab CI — skill we assign for](https://azendo.co/skills/gitlab-ci/)
* [Fastlane — skill we assign for](https://azendo.co/skills/fastlane/)
* [Codemagic — skill we assign for](https://azendo.co/skills/codemagic/)
* [TestFlight — skill we assign for](https://azendo.co/skills/testflight/)
* [Play Console — skill we assign for](https://azendo.co/skills/play-console/)
* [CodePush — skill we assign for](https://azendo.co/skills/codepush/)

## Tell us what your roadmap needs App Store Connect for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)