AppForShareCreate a free account

One link that always installs the newest build

Pro and Team

Every upload has its own link, which is right for a single build and wrong for a QR code printed on a card or pinned in a chat. A channel link never changes: it opens whatever build is in the channel now.

Example

Shop app channels

  • Beta2.5 (121), iOS and Android
  • Live2.4 (118), iOS and Android
  • Linkappforshare.io/c/...
An iPhone gets the iOS build, an Android phone the Android build, a computer sees both.

Made for

  • Teams that pin a "latest beta" link in Slack or a client chat
  • Apps tested at events or in shops with a printed QR code
  • Projects with both an iOS and an Android build

What it ends

  • Sending a new link to every tester after every build
  • Testers installing an old build from a link in last month's chat
  • Two QR codes, one for iPhone and one for Android

How it works

  1. Step 1

    Create channels

    For example Beta and Live, per project. Each gets a link and QR code that stays the same.

  2. Step 2

    Promote builds

    Put a build into a channel from the build page, or from the CLI, GitHub Action or Fastlane plugin in CI.

  3. Step 3

    Roll the link back

    Put an older build back into the channel when a release goes wrong. The link opens it at once.

Stop sending a new link after every build. An AppForShare channel, such as Beta or Live, has one link and QR code that always open the newest build put into it, on iPhone and Android. Watch on YouTube

iPhone and Android behind one link

iOS and Android builds are separate projects that share channels when they are paired. Pairing is automatic when the bundle ID and package name match, or you pair them by hand on the Testing page.

iPhone testers in TestFlight

If your iPhone testers use TestFlight, add its public link to the channel. iPhones and iPads then go to TestFlight while Android phones still get the newest APK, from the same link and QR code.

An address you pick

Give the channel a readable address such as appforshare.io/c/acme-beta from the Address button, the CLI (channel-address), the CI API or the MCP server. The old address redirects for 30 days, the in-app update check on it keeps working, and an address is never given to anyone else.

A broken build is skipped

Retire a build that should not be used and channels skip it: if it was the newest in a channel, the channel link opens the build before it until you put a fixed one in.

Testers follow a channel by email

The channel page and the install page of its newest build have an "Email me new builds" box. People confirm by email first, then get one plain email when you put in a new build, at most one every 6 hours, in the language of the page, with a one tap way to stop. You see how many follow, with masked addresses, and can remove anyone. Up to 200 followers per channel on Pro and 2,000 on Team. Private projects keep invites only.

One channel on Free

A Free account gets one channel with the same stable link and QR code. The builds in it still expire after 7 days, so between uploads the link says there is no build. More channels, a custom address, rollback and email followers come with Pro.

Good to know

Questions

Can CI promote a build?
Yes. The CLI, GitHub Action and Fastlane plugin can upload into a channel. See the CI guide.
Does the link expire?
Channel links stay live while your Pro or Team plan is active.
Can the link have a readable address?
Yes. Pick one such as /c/acme-beta: 3 to 40 lower case letters, digits and hyphens. The old address redirects for 30 days.

Read next

Try it on your own app

Free account in a minute. Pro starts with a 7 day free trial.

More features