For agencies and freelancers
Deliver app builds to clients and get every version signed off
Install links for every iOS and Android build, a client portal opened by email, and online sign-off tied to the exact build the client tested. When someone asks who approved what, you have the signed PDF.
From kickoff to approved release
Kickoff
Add the client to the project and write the kickoff agreement. They sign it online from an emailed link, no account or password.
Build and deliver
Share tasks on a board the client can see, then deliver versions: an AppForShare build with an install link, a file or a link.
Sign-off
Ask for sign-off on a version. The text names the build, its version and the SHA-256 of the exact .ipa or .apk the client tested.
Record
Every signature becomes a sealed PDF. Anyone can check a PDF on the public verify page, and you can download an evidence report per project.
What TestFlight and file links do not give you
TestFlight covers Apple devices only and needs every client in App Store Connect. A file link has no record of who installed or approved which version. AppForShare puts delivery, feedback and approval in one place.
Install links clients can use
One link or QR code per build for iPhone and Android. Clients install private builds too, without being on your tester list.
Client portal by email link
Clients sign in with a single use emailed link. They see shared tasks, every delivery and version, and leave feedback per version.
Task board
To do, In progress, In review, Done. Mark a task "Client and team" to show it in the portal, keep the rest internal.
Agreements and sign-offs
A kickoff agreement, an agreement per delivery and a sign-off per version, signed by drawing or typing, with consent and time recorded.
Sealed PDFs and verify page
Signed PDFs carry the AppForShare Document Seal, and anyone can check one on /verify by its SHA-256 in the browser.
Reminders
Unsigned agreements and sign-offs get a reminder after 3 days and one more at 7 days, then none.
Your brand on install pages
Team plans add a custom domain for install links and a white label install page with your logo and colors.
Client store access
Team plans can send the client an invite link to connect their own App Store Connect or Google Play account, with an app allowlist and an activity log.
Store readiness on every build
Each upload is checked against current App Store and Google Play rules, so a client never gets a build the store would refuse for a known reason.
Pro
$12 a month
For freelancers. 2 active client projects with portal, agreements, sign-offs, sealed PDFs and evidence reports, plus links that stay up while you are subscribed.
Team
$39 a month
For agencies. Unlimited client projects, 5 seats with roles, a custom domain and white label install pages, and client store connection invites.
Yearly billing costs 10 months. Full limits on the pricing page.
Questions
- Does my client need an account?
- No. Clients open the portal from an emailed link that works once. A new link can be requested any time from the portal sign in page while they are the client on a project.
- What does a version sign-off contain?
- The project, delivery, version number and date, the build platform, version and code, the bundle id or package name, the SHA-256 of the .ipa or .apk, and the release notes. The server refuses a signature if the text changed after the client opened it.
- Is the signature legally binding?
- AppForShare records who signed what and when: the exact text and its SHA-256, the name, the email proven by the sign in link, the signature, the consent line, IP address, browser and time. Whether that is enough for your contract depends on your law and your agreement. It is not legal advice, and you write the agreement.
- How many client projects can I run?
- Pro includes 2 active client projects (active or paused; completing a project frees its slot). Team has no limit and adds seats, roles, a custom domain and a white label install page.
- Can I show the project to my client without my internal tasks?
- Yes. Only tasks marked "Client and team" and comments marked visible to the client appear in the portal. Everything else stays with your team.
Check a build before it goes to a client with the free IPA inspector or APK analyzer.