Do testers need an account?

Testers of private projects are invited by email. Public links still install with no account at all.

How often can I remind someone?

One reminder email per tester per project in 12 hours.

Know who has installed the build, and remind the rest

Team

Sending a build is the easy part. Finding out who actually installed it, before the client call, is the slow part. Tester groups give each project a clear list: not invited, invited, opened the link, on an older build, has the newest build.

Start free See plans

Example

Client QA, Shop app

Has the newest build5 testers
On an older build2 testers
Opened the link1 tester
Invited1 tester

Made for

Agencies with a client QA group per app
Teams that test with the same people every release

What it ends

Ticking the same testers on every new project
Asking in a chat who has installed build 45
Testers still reporting bugs from last week's build

How it works

Step 1
Create a group
Name it, for example Client QA or Internal, and add testers by email.
Step 2
Give it projects
Give the group its projects in one step. Private projects open only for invited testers, who get an email on each new build.
Step 3
Follow status and remind
See each tester's status per project and send a reminder in one click, at most one per tester per project in 12 hours.

Works with TestFlight too

Link a group to an external TestFlight group and the same members are kept in step there, with Apple's status per tester.

Good to know

Tester management is on Team. Pro and Free share builds by link and QR code without per tester tracking.

Questions

Do testers need an account?: Testers of private projects are invited by email. Public links still install with no account at all.
How often can I remind someone?: One reminder email per tester per project in 12 hours.