Inviting Testers
Once your build is on TestFlight, it’s time to invite testers. This guide covers both internal and external testing.Internal vs External Testers
| Aspect | Internal | External |
|---|---|---|
| Who | App Store Connect team members | Anyone with an email |
| Limit | 100 | 10,000 |
| Apple review | Not required | Required (first build only) |
| Access speed | Immediate | 24-48 hours (first time) |
Internal Testers
Who Can Be Internal Testers?
Only people who are part of your App Store Connect team with roles like:- Admin
- App Manager
- Developer
- Marketing
Adding Internal Testers
Enabling for Internal Testers
- Go to TestFlight → Internal Testing
- Check the checkbox next to each internal tester
- They’ll receive an email invitation
External Testers
Adding Individual Testers
Using Public Links
For wider distribution, use a public link:- Create an external group
- Enable “Public Link”
- Copy and share the link
External Review (First Time)
The first build for external testers requires Apple review:What Apple Checks
- App doesn’t crash on launch
- Basic functionality works
- No obvious guideline violations
What to Provide
- Beta App Description: Brief description for testers
- Feedback Email: Where testers send feedback
- Contact Info: For Apple to reach you if needed
- Notes: Anything Apple should know
Review Timeline
- Usually 24-48 hours
- Can be faster or slower depending on volume
After Approval
Subsequent builds for the same version typically don’t need re-review unless:- You significantly change the app’s functionality
- You add new features that might need review
- Apple requests it
Managing Tester Groups
Creating Groups
Organize testers by purpose:- Friends & Family — Close contacts for early testing
- Power Users — Experienced testers
- Focus Group — Specific demographic
- Bug Hunters — Technical testers
Group Settings
Each group can have:- Automatic distribution (new builds sent automatically)
- Specific build assignment
- Custom “What to Test” instructions
Removing Testers
- Go to the tester in TestFlight
- Click “Remove” or “Delete”
- They lose access immediately
What Testers Experience
Invitation Email
Testers receive an email from Apple with:- App name
- Your custom message (if provided)
- “View in TestFlight” button
Installing Your App
- Tester downloads TestFlight app (if not already installed)
- Clicks “Accept” on your invitation
- Installs your app
- App appears on home screen with orange dot
Updates
When you upload a new build:- Testers see “Update Available” in TestFlight
- With automatic distribution, it may auto-update
- They can always roll back to previous builds
Gathering Feedback
Built-in Feedback
Testers can:- Take a screenshot in your app
- Shake device or tap TestFlight notification
- Write feedback and send
Crash Reports
When the app crashes:- TestFlight collects crash data
- View in App Store Connect → TestFlight → Crashes
- Helps identify issues to fix
External Feedback Channels
Consider also using:- A feedback form in your app
- Discord or Slack channel
- Google Form or Typeform
- Direct email
Best Practices
Start small, then expand
Start small, then expand
Begin with close contacts who’ll give honest feedback. Expand to larger groups after fixing initial issues.
Communicate with testers
Communicate with testers
Let testers know when new builds are available and what changed. They’ll test more actively if they feel involved.
Respond to feedback
Respond to feedback
Even a simple “Thanks, we’re looking into it” encourages more feedback.
Set expectations
Set expectations
Tell testers what you want them to focus on. General “use the app” feedback is less actionable than specific questions.
Tester Requirements
Testers need:- iOS device (iPhone or iPad)
- iOS 13.0 or later (for TestFlight)
- TestFlight app (free from App Store)
- Apple ID
- Your invitation
Testers don’t need a developer account. Just a regular Apple ID.