AppForShare

Firebase App Distribution alternative: when a link is simpler

· 11 min read

Firebase App Distribution alternative: when a link is simpler

Firebase App Distribution is a sensible default for a lot of mobile teams. It is part of the Firebase console many apps already use, it covers iOS and Android, it costs nothing, and it plugs into the Firebase CLI, fastlane and the Android Gradle plugin. So when people search for a Firebase App Distribution alternative, it is usually not because the product is bad. It is because one part of the flow does not suit the people who have to install the build.

This article goes through what Firebase App Distribution does well, where teams run into friction, and when a plain install link is the simpler choice. Firebase details were rechecked against the Firebase documentation on November 2, 2026.

What Firebase App Distribution does well

  • Free, with large files. App Distribution is listed as no-cost on the Firebase pricing page, and binaries can be up to 2048 MiB.
  • One console for both platforms. Android APKs and AABs and iOS IPAs are managed per app inside the same Firebase project.
  • Good tooling. Uploads work from the console, the Firebase CLI, fastlane, the Gradle plugin and a REST API. The CLI also adds and removes testers and creates groups.
  • Tester groups, invites and invite links. You add testers by email, by CSV or into groups, or post an invite link where testers add themselves.
  • Optional SDK. Basic distribution needs no SDK. With the beta SDK, the app can alert testers to new builds, and on Android testers can send in-app feedback with an automatic screenshot.
  • UDID help on iOS. During onboarding, iOS testers install a Firebase profile that registers their device, and you can export every UDID as a CSV for Apple.
  • Crashlytics. If the app uses Crashlytics, you get stability data for each distributed build.
  • AI testing on Android. The App Testing agent (preview) lets you write test goals in plain language and has Gemini run them on devices, with 200 tests a month per project at no cost during the preview (App Testing agent).
  • An MCP server. Firebase has its own MCP server for AI coding tools. When we read its tool list on November 2, 2026, it covered products such as Crashlytics, Firestore and Remote Config; App Distribution tools were not in that list.

If your app already uses Firebase, your testers all have Google accounts and you send builds to the same group every week, it works well and you probably do not need to change anything.

Where teams hit friction

Testers must sign in with Google

To accept an invitation, a tester signs in with a Google account, and the same account is used to install, get alerts and send feedback. For an internal team on Google Workspace that is invisible. For a client on Microsoft 365, a tester who does not want to link a personal Gmail to your project, or a stakeholder who just wants to tap a link before a meeting, it is one more step that someone has to explain. Company Workspace accounts can also be blocked by their admin, which shows up as a 403 "Contact your admin for access" error. Firebase notes that by default an invitation can be accepted once and with any Google account, which surprises people who expected it to be tied to the invited address. The details are in Firebase App Distribution without a Google account.

Invitations, expiry and the tester app

Invitations expire if they are not accepted within 30 days, and you renew them from the console. Releases are removed after 150 days, and there is a cap of 500 testers per project and 200 per group, raised on request. On Android, testers use the App Tester app to install releases. On iOS, the flow is open the email in Safari, sign in, install the Firebase profile, register the device, then install the build from a web clip on the home screen. Each step is reasonable. Together they are a lot for a tester who only needs one build once. All the numbers are in Firebase App Distribution limits.

Project setup comes first

Distribution lives inside a Firebase project, with an app registered for each bundle ID and package name. For an agency shipping a dozen client apps, that is a dozen projects or a crowded shared one, plus deciding who in the client's company gets console access. For a one off build, setting up a project can take longer than the test itself.

iOS still needs Ad Hoc signing

This is not a Firebase limit, it is Apple's. Any tool outside TestFlight installs iOS builds the same way: the build must be signed Ad Hoc, Development or Enterprise, and for Ad Hoc and Development the device UDID has to be in the provisioning profile. Firebase helps collect the UDIDs, but you still add them in the Apple Developer portal, make the profile again and rebuild or re-sign the build with it. Switching tools will not remove the registration step. See iPhone UDID problems in Firebase App Distribution and Ad Hoc device registration.

AAB testing has extra setup

To distribute Android App Bundles, the Firebase app must be linked to the matching app in Google Play, because Firebase uses Play's internal app sharing to produce installable APKs. Firebase's troubleshooting page lists the conditions: Owner or Admin access in Play, the same package name, and an app that has passed review and is published on a Play track. Testers also turn on Internal app sharing in the Play Store app once. If your app is not on Play yet, or the client owns the Play account, uploading an APK is simpler.

Feedback is Android only and routing it takes code

The in-app feedback SDK is Android only and in beta, and testers sign in with Google to use it. Sending feedback or new device alerts to Slack, Discord or Jira means writing Cloud Functions, which needs the Blaze plan.

When an install link is simpler

An install link service skips the invite and account steps. You upload the build and get one URL and a QR code. The tester opens it on the phone and installs. On Android they allow installs from unknown sources once; on iOS the device must already be in the profile. That fits:

  • Client reviews. The person approving the app should not need a Google account or a tester app. See sending app builds to clients.
  • Quick one off builds for a designer, a support colleague or a beta user who reported a bug.
  • Agencies with many small apps, where one project per app in Firebase is overhead.
  • Teams that already use Crashlytics or another tool for crashes and just need the install step.

An install link is not always better. If you want automatic in-app screenshots on Android, Crashlytics stability data next to each build, device specific APKs from an AAB or an AI agent that runs tests on Android devices, those come from Firebase.

Comparison

QuestionFirebase App DistributionAppForShare
What the tester needsGoogle account, invite email; App Tester app on Android, Firebase profile on iOSThe link or QR code; invited testers on Team confirm by email link
Self sign upInvite links, then Google sign inJoin links with email confirm, domain limit, cap and pause (Team)
Setup before first uploadFirebase project with the app registeredAn account, or none for a quick guest upload
Price and file sizeNo-cost, up to 2 GBFree up to 150 MB; Pro 2 GB; Team 4 GB
How long builds stay installable150 daysFree 7 days; Pro and Team while subscribed
iOS signingAd Hoc or Enterprise, UDIDs in profileSame; plus device registration on Apple, profile remake and re-signing with the new profile, no rebuild (Pro and Team)
Android formatsAPK, or AAB with a Play linkAPK, or AAB turned into one universal APK with no Play link
New build alertsOptional SDK, Google sign inUpdate check endpoint with code snippets, no SDK (Pro)
Tester feedbackAndroid SDK (beta), automatic screenshot, Google sign inInstall page and in-app feedback link, iOS and Android, no sign in (Free; video Pro)
Crash dataCrashlytics per buildNo crash reporting; a link to your crash dashboard per project (Pro)
AI testingApp Testing agent runs tests on Android (preview)AI test plan for a person to run; export to App Testing agent YAML or Maestro (Pro)
Stable latest build link, link controlsNoChannels, pause, stop date, install cap (Pro)
Best forTeams already on Firebase with recurring tester groupsClients, outside testers, agencies with many apps

Moving a CI step from Firebase to an install link

If your pipeline calls the Firebase CLI today, the swap is one line. For example, in GitHub Actions:

# before
- run: firebase appdistribution:distribute app-release.apk --app "$FIREBASE_APP_ID" --groups "qa"

# after
- name: Share build
  run: npx --yes appforshare@1 upload app/build/outputs/apk/release/app-release.apk --groups "QA" --notes "${{ github.event.head_commit.message }}"
  env:
    APPFORSHARE_TOKEN: ${{ secrets.APPFORSHARE_TOKEN }}

--groups and --testers need CLI 1.9.0 or later and the Team plan; without them the upload still gives you a link to share. The CLI also has testers, groups and distribute commands like Firebase's. A Gradle plugin with appforshareUpload<Variant> tasks is on the Gradle Plugin Portal (io.appforshare.upload), and fastlane actions for testers, groups and UDIDs are in plugin 1.2.0. Keep both for a sprint if you want: there is no reason a build cannot go to Firebase for the internal group and to a link for the client. More options are on the CI docs page and in uploading builds from CI.

Things to check before you switch

  1. Who your testers are. If they are all on Google Workspace and already onboarded, the friction above may not apply to you.
  2. Whether you rely on the SDK. Remove the App Distribution SDK calls only once something replaces the alerts and feedback you use.
  3. Your iOS UDID list. Export it from Firebase (Export Apple UDIDs) and import it into the new tool. The devices are already in your Apple account.
  4. Your tester list. Save emails and groups as a CSV so you can import them in one go.
  5. Android format. If you only produce AABs, check that the new tool accepts them, or add a step that builds an APK.

The full checklist is in moving off Firebase App Distribution and the product steps are on Move from Firebase.

Other services to look at

Updraft, from Apps with love AG in Bern, Switzerland, has run since 2012 and hosts files in Switzerland. As listed on November 9, 2026, Starter is free (1 project, 3 builds, 500 MB, 100 installs a month), Pay as you go is $5 a month plus $5 per GB stored with 1,000 installs a month, Professional at $49 a month plus storage adds re-signing and App Store and Google Play upload, and Enterprise (on quote) adds single sign on and your own storage bucket. Users are unlimited on every plan, and it also takes Windows and macOS packages. See AppForShare vs Updraft and Updraft pricing in 2026.

AppForShare as a Firebase App Distribution alternative

AppForShare is a standalone install link service. It does not connect to your Firebase project and has no in-app SDK. You upload an .apk, an .aab or an Ad Hoc, Development or Enterprise signed .ipa, and get a link and a QR code that testers open on the phone. No tester account and no tester app needed.

  • Free: password protected links that last 7 days, files up to 150 MB, feedback with screenshots from the install page and from inside the app with the in-app feedback link, the UDID finder, and import of Firebase's UDID file.
  • Pro ($12 a month): links live while subscribed, CI uploads, release notes, channels with a stable link, install link controls, install analytics, webhooks to Slack, Microsoft Teams or Discord, the in-app update check, screen recordings in feedback, an MCP server, test plan export and a crash dashboard link.
  • Team ($39 a month): private projects for invited testers, join links, tester groups, tester CSV import, testers and groups from the CLI, a tester app without a store, and hands free device setup, where devices that enroll are registered on Apple, the Ad Hoc profile is remade and the GitHub iOS build starts, or, with no GitHub build, the newest iOS build is re-signed with the new profile.
  • The free IPA inspector shows which devices a build includes before you share it.

See AppForShare vs Firebase App Distribution for a feature by feature view, pricing for every limit, or sign up free and send your next build as a link.

Keep reading

App Distribution Platform · · 5 min read

AppForShare File Size and Upload Limits

AppForShare limits the size of each build you upload by plan: 50 MB without an account, 150 MB on the Free plan, 2 GB on Pro and 4 GB on Team. Accounts also have a storage total, and every plan...