iOS and Android app distribution

Share signed mobile builds with testers

Upload a signed iOS IPA or Android APK, review package details, keep Release history, and create tester links with the access rules you need. DistKit does not sign or re-sign packages.

DistKitWorkflow overview
AppCurrent AppDurable product record
ReleaseCurrent ReleasePackage report attached
AudienceTester linkIndependent policy
ReadyCreate the intended tester linkPassword · Expiry · Delivery-handoff limit BlockedKeep the report and replace the packageNo usable delivery path until corrected
Signing assets, platform eligibility, and tester authorization remain with the Release owner.
Reads IPA and APK package metadata Keeps App and Release history Applies policy before file delivery

For QA cycles and client reviews

Use your existing signing process. Manage the build handoff in DistKit.

QA teams

Keep recurring builds in one App history and give each QA audience an explicit Release link.

Independent developers

Inspect provisioning details before sharing a build with collaborators or a small tester set.

Agencies

Separate client-review links by password, expiry, request limit, and current Release.

Signing remains with the publisher.

DistKit analyzes the package you provide and controls its delivery path. Apple certificates and profiles remain in Apple Developer; Android signing keys and export settings remain in your build pipeline.

DistKit
Package report · Release records · Link policy · iOS and Android delivery
Publisher tools
Apple profiles or Android signing keys · Package export · Tester authorization

Check the fit before your first upload

Review the iOS distribution steps, storage and access controls, or plan limits before you start.

Analyze your first mobile package.

Create a workspace, upload a signed IPA or APK, and review its package report before sharing.