---
title: "TestFlight | Skills We Assign For | Azendo"
description: "TestFlight for iOS beta distribution — internal and external testing, review timing, and the Azendo roles assigned for it."
url: "https://azendo.co/skills/testflight/"
---

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

# TestFlight.

TestFlight is Apple's beta distribution service. Builds are uploaded to App Store Connect and shared with internal testers immediately, or with up to ten thousand external testers after a lighter review than a store release.

## Where TestFlight fits on a long engagement.

The distinction that matters for planning is internal versus external. Internal testers — up to a hundred people on the team — get builds with no review at all, usually within minutes. External testers require a review of the first build in a version, which is faster than a store review but is still an external dependency with variable timing.

Build expiry catches teams out. TestFlight builds stop working after ninety days, so a testing programme needs a cadence rather than a single distribution, and testers who were not warned experience it as the app breaking.

## What an assigned team does with TestFlight.

Feedback from a beta is only useful if someone is responsible for triaging it. Unowned TestFlight feedback accumulates, testers stop reporting because nothing happens, and the programme quietly becomes a distribution channel rather than a testing one.

Making that a named responsibility with a cadence is a QA function rather than a developer one, which is why [outsource qa testing](https://azendo.co/services/qa-engineering-and-test-automation/) capacity is scoped alongside mobile work.

## What we use TestFlight for.

* Getting builds to the team immediately Internal distribution with no review, so a fix can be verified the same day.
* Structured external beta A tester group with a release cadence that accounts for build expiry.
* Feedback that is actually triaged Tester reports owned by someone, so the programme keeps producing signal.

## How TestFlight capacity is assigned.

Beta distribution is set up as part of the release path, scoped with the mobile and QA capacity rather than arranged at the first release.

## Roles we assign TestFlight 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/)
* [App Store Connect — skill we assign for](https://azendo.co/skills/app-store-connect/)
* [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 TestFlight 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/)