Features
From the first test build to the store
AppForShare started as the quickest way to put a build on a phone. Today it also builds on your own GitHub Actions, registers test devices on Apple, edits store listings and sends versions for App Store review, always with your own keys and a person pressing the button.
Builds on GitHub Actions
ProWe write the workflow and secrets, you merge one pull request. Builds go to testers, TestFlight or a Google Play track, on GitHub hosted or your own runners, and failed runs are explained.
Flutter builds on GitHub Actions
ProFor a Flutter repository the GitHub builds setup writes a workflow that sets up your Flutter version and builds iOS and Android, on your own GitHub Actions minutes.
Flutter facts and checks
FreeBuild mode, engine or Dart version, an obfuscation hint and the Impeller flag on every Flutter build, plus readiness lines for debug and profile builds.
Security scan on every build
ProHardcoded keys (shown masked), risky Android and iOS settings and library versions with a known advisory, each with an OWASP MASVS category and a fix. Fail a pipeline on it with the CLI.
Connect Expo (EAS builds)
ProRun one eas webhook:create command and each finished EAS internal build lands in AppForShare with its install link, channel and readiness check.
Connect Codemagic
ProPaste a Codemagic API token once, map a Codemagic app and workflow to a project, and finished builds arrive with their install link, channel and readiness check.
Send store builds to TestFlight and Google Play
ProUpload the App Store .ipa or the .aab once, then send it to TestFlight or a Google Play testing track (Pro) or a production draft (Team).
TestFlight groups and beta review on send
TeamAn Admin picks TestFlight groups and ticks beta review on Send to TestFlight; once Apple has processed the build, it is done as asked. Apple still reviews.
TestFlight feedback in your inbox
TeamScreenshot and crash feedback from TestFlight testers next to install page reports, with Linear, Jira, blockers and tasks.
iOS device registration
ProOne link collects UDIDs, one click registers them on Apple and adds them to your ad hoc profile. Testers get an email when their build is ready.
Hands free device setup
TeamA device sent through the onboarding link is registered on Apple, the ad hoc profile is remade and the GitHub iOS build starts, or the newest build is re-signed. The tester gets the install email.
Store listing editor
ProText, keywords, screenshots and graphics for both stores, with limits checked, every change kept and AI translation you read first.
App Store submission
ProBuild, export compliance, review details, release type and a checklist of what Apple needs, then you send it for review.
Google Play releases
ProTracks, release notes, promotion and saved release defaults on Pro. Staged and scheduled production rollouts, halt, resume, complete and testers on Team.
TestFlight tester sync
TeamLink a tester group to an external TestFlight group and members stay in step, with Apple's status per tester.
Tester app with notifications
TeamTesters add their builds page to the home screen and get a push notification for every new build. No store app, no account.
Tester groups and status
TeamNamed groups of testers, status per tester for every project, and reminder emails in one click.
Join links for testers
TeamOne link testers use to join a project or a tester group: they confirm their email and get the newest build. Domain limit, cap and pause.
Beta and Live channels
ProA stable link and QR code per channel, the same for iPhone and Android. Promote or roll back the link in one click or from CI.
Build history page
ProAn opt in page per app with its last 20 builds, iOS and Android side by side, release notes, channels and an Install button each.
Tasks and activity feed
TeamA task board on every project, tasks from tester feedback linked to builds, and a feed of who did what.
Feedback to Linear and Jira
ProOne click turns a tester report into a Linear or Jira issue with the device facts and screenshots attached.
Release checklist, approvals and blockers
TeamOne checklist ticked per build, with named approvers. Live, Play production and App Store review wait for every step, approval and blocker.
Release page per version
TeamBuilds, readiness, checklist and approvals, App Store review, Google Play rollout with Android vitals, and a timeline for one version. Read only on Pro.
Install link controls
ProPause a link, stop it after a date or cap its installs, per build. Installed apps keep working.
Several links per build
ProExtra share links to the same build, one per client or group, each with its own password, stop date, install cap and count.
Retire a test build
ProRetire a broken build with a note: its link sends testers to the newest build, channels skip it and the update check reports it.
TestFlight and APK in one link
ProAdd the TestFlight public link to a channel: iPhones open TestFlight, Android phones get the newest APK, same link and QR.
Install page in 13 languages
FreeInstall and channel pages in 13 languages, from Hindi, Urdu and Arabic to Chinese, Portuguese (Brazil), French, Turkish, Vietnamese and Russian, picked from the phone.
In-app update check
ProYour test build asks its channel for the newest build and offers to install it. A few lines of code, no SDK.
.aab uploads
FreeFlutter and React Native build an .aab by default. Upload it as it is and testers install an APK made from it.
MCP server for AI tools
ProClaude Code, Cursor, Codex and VS Code can upload builds, find install links, read readiness and check App Review status.
Tester feedback with screenshots
FreeA Send feedback button on every install page. Screenshots testers draw on, device and build attached, an inbox for your team.
In-app feedback link
FreeYour test build opens one web address from a debug menu or a shake. Testers report on the exact build and screen, with screenshots. iOS and Android.
AI test plan for each build
FreeUp to 15 test tasks per build, from new permissions, OS changes, store check findings and your notes. Tick them off as a team.
Diawi compatible upload API
ProThe same fields and status codes as the Diawi API. A script or plugin that uploads to Diawi uploads here after a URL and token change.
Remember my iPhone
FreeCheck the iPhone once, then every iOS install page says whether the build includes it, with a way to send it to the developer when it does not.
Install help and why it failed
FreeBlocking notes above Install when the build cannot work on that phone, and a short install help list for iPhone and Android.
Email the install link
ProUp to 5 addresses per build, from the build page, CLI, CI or MCP. One plain mail per address, no tracking.
Custom channel address
ProPick /c/acme-beta instead of a random code. The old address redirects for 30 days, and addresses are never reused.
Verified publisher
ProOne DNS record and your install pages say "Shared by Acme, verified owner of acme.com". Rechecked weekly. It proves the domain, not the app.
Daily install email
ProInstalls since yesterday by build, device and country, once a day. No installs, no email.
Zipped .app upload
FreeA .zip with one .app folder becomes an .ipa. File modes and links are kept, so the app still runs.
Manage link for guest uploads
ProGuest uploads come with a private manage link: installs, time left and tester feedback, end the link sooner, delete or restore.
Test accounts on the install page
ProUp to 3 test logins per build or channel, shown on the install page after the page password or an access code, stored encrypted.
Telegram notifications
ProYour own Telegram bot posts new builds, installs and tester feedback to a group or channel, with the install link.
Permissions in plain words
FreeInstall pages list a build's permissions in plain words in 13 languages, with the app's own iOS reasons; the build page marks new ones.
Reply to testers and star ratings
ProReply to a tester's report and they get one email in their language and can answer back (Team). Testers rate each build 1 to 5 stars (Pro and Team).
Follow a channel by email
ProAn "Email me new builds" box on a channel link: people confirm once, then get one plain email per new build, at most one every 6 hours.
Download button for a README
FreeCopy an "Install test build" button as Markdown or HTML; a channel button shows the newest version (Pro and Team).
Store pages
ProPrivacy policy, support and account deletion pages per store app, written from your answers and your build, with the URLs filled into your listing.
Check a build before upload
Freenpx appforshare check runs the store readiness, install and security checks on your computer, with nothing uploaded and no account needed.
Token scopes and CLI tools
ProAPI tokens can be full, upload only or read only, with an end date of 1 to 365 days; tokens, restores and webhook deliveries from the CLI.
Upload from Claude or ChatGPT
ProYour assistant makes a one time upload link, you drop the build in any browser, and it lands in your workspace; or it uploads from a public URL.
Passkeys and email code sign in
FreePasskeys (fingerprint, face or device PIN) and a one time email code, next to password, Google, GitHub and two step sign in.
Free build tools
FreeAAB inspector, APK signing fingerprints and an ExportOptions.plist generator, free in the browser with nothing uploaded.
How reports work
FreeEvery report needs a reason, an automated review helps our team sort them, a person decides; the hold rule differs on Free and paid plans.
Malware check on every upload
FreeClamAV opens each .apk and .ipa and a SHA-256 lookup asks MalwareBazaar about the file, right after the link is issued. A match is held for a person to review. Every plan, guests included.
AppForShare Android store
FreeA public Android store at store.appforshare.io: each release built from your source by our workflow in your GitHub Actions, reviewed automatically, signed, and also in F-Droid clients.
Re-sign iOS builds
ProRe-sign an uploaded iOS build with a new ad hoc, development or enterprise profile, as a new build. The original, its link and its SHA-256 stay as they were.
Single sign on (SAML and OpenID Connect)
TeamSAML 2.0 or OpenID Connect sign in, company domain proven by DNS, identity provider groups mapped to roles and tester groups, and an option to require it.
Require two step sign in
TeamOne rule makes every member use an authenticator code or a passkey before they can open the workspace. The member list shows who has it.
Send to Microsoft Intune
TeamHand an enterprise or ad hoc .ipa or a signed APK to your own Intune as a line of business app, new or as a new version. Assignment stays in Intune.
Choose where build files are stored
TeamNew uploads go to our storage in the United States or the European Union, or to your own S3 compatible or Google Cloud Storage bucket.
Mac and Windows builds
ProShare .dmg, .pkg and zipped .app builds for macOS and .msix, .appx and .msi builds for Windows, with a download page that shows the size, SHA-256 and signing facts.
Workspace address
ProInstall, channel, build history and join pages on <name>.appforshare.io, with your workspace name and icon at the top.
Automatic clean up of old builds
ProKeep the newest N builds per platform and/or remove builds older than 30 to 180 days, once a day, with the usual 7 day restore window.
Tester email from your own mail server
TeamTester facing emails go out through your own SMTP server and From address. Send a test first; a failed send falls back to our sender once.
Webex notifications
ProNew builds, installs, tester feedback and store changes arrive in a Webex space as short messages with a link.
Also in AppForShare
Install links and QR codes
Upload an .ipa or .apk and testers install it from a link. No account needed for a first upload.
Client projects
Task board, deliveries, feedback and signed approvals in a client portal opened by an emailed link.
CLI, GitHub Action and Fastlane
Upload from CI with the store readiness result in the pipeline.
Free tools
IPA inspector, APK analyzer, UDID finder and app icon generator, in the browser.