Does the person need an account?

No. They open the link on the phone and install, like any install link.

Can I protect the link with a password too?

Yes. The CLI takes --password, the GitHub Action a password input and fastlane password:. Send the password through another channel.

AppForShare Create a free account

Send the install link by email, right from the upload

Pro and Team

Sometimes the quickest way to get a build to a client or a designer is an email with the link. Copying the link from a CI log into a mail client for every build is the slow part.

Name up to 5 addresses when you upload, or later from the build page, and each one gets a short mail with the install button. An address gets each build once, even if a job runs twice.

Start free See plans

Example

Email the link

[email protected]Sent by CI, 09:12
[email protected]Sent by Omar, 11:40
[email protected] againSkipped, already sent

Up to 5 addresses at a time, 50 a day per account.

Made for

Freelancers and agencies that send builds to one or two client contacts
CI jobs moving from Diawi's callback_emails
Teams on Pro that do not need full tester lists

What it ends

Copying the install link out of a CI log into an email
Sending the same build twice because a job was retried
Promotional looking mails that land in spam

How it works

Step 1
At upload
CLI upload --email [email protected],[email protected], the GitHub Action input email, fastlane email:, or callback_emails on the Diawi compatible API. The mails go out when the build is ready.
Step 2
Later
The Email the link card on the build page, appforshare email <id> --to, POST /api/ci/builds/:ref/email or the MCP tool email_build_link.
Step 3
See who got it
The build page card lists every address it was sent to, by whom and when.

A plain transactional mail

Each mail names who shared the build, the app and version, the release notes if there are any, and an Install button. It says why the person got it. There is no tracking in it and nothing else to sell.

To keep it that way there are limits: up to 5 addresses per call, one mail per build and address, and 50 addresses a day per account.

Testers or email?

Projects open only to invited testers refuse emailed links: add those people as testers instead, so they get their own access (Team). Links that no longer work cannot be emailed. For a group of people who should get every build, tester lists and groups on Team are the better fit.

Good to know

Up to 5 addresses per call and 50 a day per account.
Not for private (testers only) projects or expired links.
Each address gets a build once. A later build is a new mail.

Questions

Which plan do I need?: Pro or Team.
Does the person need an account?: No. They open the link on the phone and install, like any install link.
Can I protect the link with a password too?: Yes. The CLI takes --password, the GitHub Action a password input and fastlane password:. Send the password through another channel.