Aloft

Over-the-air build distribution

Hand a build to a phone without a store in the middle.

Drop in an .ipa or .apk. Aloft reads the bundle, writes the install manifest iOS needs, and gives you one link. Your tester opens it on their device and the app lands.

  1. UPLOADStreamed straight to disk. Nothing is sent anywhere else.
  2. READBundle id, version, icon and signing type, pulled from the file itself.
  3. SHAREA short link and a QR code, both good until the expiry you set.
  4. INSTALLiOS gets a signed manifest handoff, Android gets the APK.

Check in a build

.ipa or .apk, up to 512 MB. Links from signed-out uploads last 7 days.

Set expiry, a password, or release notes

What Aloft pulls out of a build

Enough to catch the installs that were going to fail anyway — before you send the link to twelve people.

From an .ipa

  • Bundle id, display name, marketing and build version
  • App icon, un-mangled from Apple's CgBI PNG format
  • Signing type read from the embedded provisioning profile
  • A warning when the profile is App Store signed and simply cannot install
  • How many device UDIDs an ad-hoc profile actually covers, and when it expires

From an .apk

  • Package name, versionName and versionCode from the binary manifest
  • Launcher icon resolved through resources.arsc, adaptive icons included
  • Signature schemes present: v1, v2, v3
  • A warning when the build is debuggable or v1-only
  • Requested permissions and bundled native ABIs