A beta tester app without the App Store: how testers get new builds

You ship build 42 on Tuesday morning with the fix for the login crash. On Thursday a tester reports the login crash again. After a few messages it turns out they are still on build 39, because the email about the new build landed under twenty other emails and the link in the team chat scrolled away the same afternoon.

This happens on almost every beta. Testers are often clients, colleagues from other departments or friends of the project, not people who check a release feed. When reaching a new build takes effort, they keep the one they have. This guide looks at how testers can get new builds today, what a good tester experience looks like, and how the AppForShare tester app gives testers one place for every build on iPhone and Android without a download from the App Store or Google Play.

Why testers miss new builds

The pattern is nearly always the same:

• The notice is buried. A build email competes with everything else in the inbox, and a link in a busy chat channel is out of view within hours.
• The old link still works. Testers bookmark or reopen the first link they got, which may point at an old build.
• There is no single place to look. A tester on three projects has three email threads and no view of what is new.
• Nothing tells them they are behind. The installed app keeps working, so there is no reason to look for a newer one.

The cost lands on the team: bug reports against fixed builds, time spent asking "which version are you on", and features that ship without anyone testing their final state.

The options testers have today

TestFlight

Apple's TestFlight app is the standard route for iOS. Testers install TestFlight from the App Store, accept an invite or open a public link, and the app shows new builds and can update them. It works well for iPhone testers. The limits: it covers Apple platforms only, the builds go through App Store Connect, external testing needs Apple's beta review, and builds expire after 90 days. Android testers on the same project need a different route.

Google Play testing tracks

Internal, closed and open testing tracks let testers opt in and receive test builds through the Play Store, including automatic updates. Testers need a Google account added to the track and must accept the opt in link, and the app has to be set up in Play Console. It suits teams already publishing on Google Play, less so early builds, client work or apps not yet in Play Console.

Distribution tools with a native tester app

Some build distribution services, such as Firebase App Distribution, offer their own tester app for Android, which lists builds and notifies testers. Testers install that app first, often with an account, and on iOS the setup usually differs from Android. A native app gives the deepest integration on the phone, but it is one more install and one more sign in before a tester sees a single build.

Links in email and chat

The simplest option: share an install link for each build. No setup for the tester, and it works for both platforms. It is also where the problems above come from. Every build is a new link, and nothing collects them in one place.

An installable web app (PWA)

A web page can be added to the home screen and opened like an app, with its own icon, and it can receive push notifications. Nothing is downloaded from a store and there is no store review for the tester app itself. The trade offs are real: on iPhone, push notifications need iOS 16.4 or later and only work once the page is added to the home screen, and a web app cannot install or update builds on its own. It opens the install page, and the phone does the rest.

What a good tester experience looks like

Whatever tool you use, testers should get the following:

• One place with every build shared with them, across all projects, newest first.
• One tap to the install page of the newest build, with no searching through old emails.
• A nudge when a new build arrives, on the phone, not only in the inbox.
• No account to create just to test someone else's app.

Testers also need their phone ready for test builds, which no tester app can skip:

• iPhone, ad hoc builds: the device UDID must be in the provisioning profile the build was signed with. A tester whose device was not registered cannot install the build, however they open it. The UDID finder reads it in a minute, and the guide on registering devices for ad hoc builds covers the full flow. TestFlight builds do not need this.
• Android: the APK installs from the browser, so the tester allows installs from that browser the first time Android asks. After that, new builds install the same way.

How the AppForShare tester app works

On the Team plan, you invite testers to private projects or add them to tester groups. Each invited tester gets an emailed link. Opening it shows a page called "Builds shared with you" at appforshare.io/tester: every project shared with that email address and its newest builds, each with a link to the install page. The tester does not need an AppForShare account.

That page is the tester app. It is an installable web app, not a native app from the App Store or Google Play, so testers add it to the home screen from the browser.

On iPhone

1. Open the link from the invite email in Safari. "Builds shared with you" opens.
2. Tap Share, then Add to Home Screen. The tester app now has its own icon.
3. Open it from the home screen. It opens signed in, for up to 180 days. iPhone keeps a separate cookie store for home screen apps, so the app opens through a signed start address instead of relying on the Safari session.
4. Tap "Notify me about new builds" and allow notifications. This needs iOS 16.4 or newer and the page opened from the home screen, not from a Safari tab.
5. When a new build is shared in one of the tester's projects, a push notification arrives. Tapping it opens the install page. For ad hoc builds, the device still needs to be registered first.

On Android

1. Open the link from the invite email in Chrome.
2. Chrome offers Add to home screen. Accept it, or pick it from the browser menu.
3. Open the app from the home screen. It opens signed in for up to 180 days.
4. Tap "Notify me about new builds" and allow notifications.
5. When a new build arrives, tap the notification, then install the APK from the install page. The first time, Android asks to allow installs from the browser.

What to expect from notifications

Push notifications come next to the existing new build email, not instead of it. A tester gets at most one notice per project within a quiet period, so a burst of uploads does not turn into a burst of alerts. Testers can turn notifications off at any time on the same page.

The tester app works on appforshare.io. If your install links use a custom domain, testers still get the email about new builds, but notifications from the tester page are only available on appforshare.io.

What the team sees

On Team, each project shows the status of every tester: who opened the link, who installed an older build and who has the newest one. You can send a reminder to testers who are behind instead of writing to each of them.

Tips to keep testers on the newest build

Name builds clearly

Testers see version and build numbers, so make them mean something. Raise the build number on every upload and keep the version for real milestones. A tester who sees 2.4 (118) next to 2.4 (116) knows which one is newer without asking.

Write short release notes

Two or three lines on what changed and what to test give the notification a reason to be opened. "Fixed the login crash on older Android phones, please try signing in again" gets more replies than an empty build. The guide on collecting tester feedback with screenshots covers what to ask for once they have the build.

Use channels for stable links

With Beta and Live channels, each channel has one link and QR code that always opens its newest build. Printed QR codes and pinned links stay current. If your iOS testers use TestFlight, you can put a TestFlight public link on a channel, so iPhones go to TestFlight and Android phones get the newest APK from the same link.

Add an update check inside the test build

Notifications reach testers who turned them on. For everyone else, the in-app update check on Pro and Team adds a few lines of Swift, Kotlin, Dart or JavaScript to your test build. When the channel has a higher build number, your app shows your own message and opens the install page. It needs no SDK.

Check status before a release

Before you call a build tested, look at who actually has it. If half the testers are on an older build, their silence says little about the new one. Send a reminder and wait a day.

Common questions

Is there a TestFlight alternative for Android testers?

Yes. Google Play testing tracks deliver test builds through the Play Store, some distribution tools offer an Android tester app, and install links let testers install the APK from the browser. The AppForShare tester app gives Android and iPhone testers the same page with every build shared with them, and notifications when a new one arrives.

Do testers need to install anything from the App Store or Google Play?

Not for the AppForShare tester app. It is an installable web app that testers add to the home screen from Safari or Chrome. The builds themselves install from the install page: APKs from the browser on Android, ad hoc builds on iPhone once the device is registered.

Why do notifications not work on my iPhone?

Check two things. The iPhone needs iOS 16.4 or newer, and the tester app has to be opened from the home screen icon, not from a Safari tab. Then tap "Notify me about new builds" again and allow notifications.

Do testers need an AppForShare account?

No. Invited testers open the link from their email and see the builds shared with that address. The team that shares the builds needs the Team plan for tester invites, tester groups and the tester app. See pricing.

Can the tester app install new builds automatically?

No. It shows the newest builds and sends a notification that opens the install page, where the tester installs the build. Automatic updates of test builds are a feature of store based testing, such as TestFlight and Play testing tracks.