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.
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.
From the CLI, CI and AI tools
Share a build with groups or people as you upload it: appforshare upload app.apk --groups "Client QA" --testers [email protected]. When the build is ready, the groups get its project, new addresses become testers, and everyone named gets the new build email, even when the project's notices are off. A tester gets at most one of those emails per project in an hour. The GitHub Action takes groups and testers inputs, and so do the fastlane plugin and the Gradle plugin.
appforshare testers lists, adds, imports and removes testers, appforshare groups makes and deletes groups and changes members, and appforshare distribute shares a build that is already uploaded. AI tools connected through the MCP server can list testers and groups, add or remove testers and share a build, after you confirm.
Bring your list
Import testers from a CSV file on the Testers page or with appforshare testers import: an email column, a name or first and last name columns, and a groups column. Groups that do not exist yet are made. Up to 1,000 rows per import, invites off by default, and up to 200 invites per import when you turn them on.
Coming from Bitrise
appforshare import bitrise copies your tester groups and testers from Bitrise Release Management. The CLI reads Bitrise on your own computer with your Bitrise personal access token, which is never saved and never sent to AppForShare; only group names, tester names and emails reach us. Without --app it lists your Bitrise apps, and --app takes the connected app id or the bundle id or package name.
Groups are matched by name, in any case, or made, empty ones too. A tester in two groups becomes one tester in both. --dry-run only counts, and nobody is emailed unless you add --notify. It needs CLI 1.18.0 or later.
Good to know
- Tester management is on Team. Pro and Free share builds by link and QR code without per tester tracking.
- An account can have up to 1,000 testers. One call shares a build with up to 100 groups and testers.
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.
- Can testers add themselves?
- Yes, with a join link. Post it in your beta group; testers enter an email, confirm it and land in the project or a group.
- Can CI pick who gets a build?
- Yes. upload --groups and --testers, the distribute command, the GitHub Action, fastlane and Gradle plugins all share a build with named groups and testers. It needs a Team workspace.
- Can I bring my testers from Bitrise?
- Yes, on Team: appforshare import bitrise copies Release Management tester groups and testers. Your Bitrise token stays on your computer, and no invites go out unless you ask.
Read next
Try it on your own app
Free account in a minute. Pro starts with a 7 day free trial.
More features
- Builds on GitHub Actions
- Flutter builds on GitHub Actions
- Flutter facts and checks
- Security scan on every build
- Connect Expo (EAS builds)
- Connect Codemagic
- Send store builds to TestFlight and Google Play
- TestFlight groups and beta review on send
- TestFlight feedback in your inbox
- iOS device registration
- Hands free device setup
- Store listing editor
- App Store submission
- Google Play releases
- TestFlight tester sync
- Tester app with notifications
- Join links for testers
- Beta and Live channels
- Build history page
- Tasks and activity feed
- Feedback to Linear and Jira
- Release checklist, approvals and blockers
- Release page per version
- Install link controls
- Several links per build
- Retire a test build
- TestFlight and APK in one link
- Install page in 13 languages
- In-app update check
- .aab uploads
- MCP server for AI tools
- Tester feedback with screenshots
- In-app feedback link
- AI test plan for each build
- Diawi compatible upload API
- Remember my iPhone
- Install help and why it failed
- Email the install link
- Custom channel address
- Verified publisher
- Daily install email
- Zipped .app upload
- Manage link for guest uploads
- Test accounts on the install page
- Telegram notifications
- Permissions in plain words
- Reply to testers and star ratings
- Follow a channel by email
- Download button for a README
- Store pages
- Check a build before upload
- Token scopes and CLI tools
- Upload from Claude or ChatGPT
- Passkeys and email code sign in
- Free build tools
- How reports work
- Malware check on every upload
- AppForShare Android store
- Re-sign iOS builds
- Single sign on (SAML and OpenID Connect)
- Require two step sign in
- Send to Microsoft Intune
- Choose where build files are stored
- Mac and Windows builds
- Workspace address
- Automatic clean up of old builds
- Tester email from your own mail server
- Webex notifications