Your testers read the install steps in their own language
Every plan, also without an account
Many testers are clients, shop staff or family members, not developers. "Allow installs from this browser" or "this build only runs on registered devices" is hard enough in your first language. The install page now speaks theirs.
The language comes from the phone's settings. A tester can switch at the bottom of the page, and the choice is remembered on that browser.
Example
Install page
- Phone language Urduاردو, right to left
- Phone language Hindiहिन्दी
- Phone language SpanishEspañol
- Phone language PortuguesePortuguês (Brasil)
- Phone language Chinese简体中文
- Anything elseEnglish
Made for
- Agencies in South Asia and Southeast Asia whose clients test on their own phones
- Apps tested by field staff, drivers or shop teams
- Teams with testers in Latin America, the Middle East, Turkey, Vietnam, China and Europe
What it ends
- Explaining the install steps again on a call
- Testers stuck at the "unknown sources" prompt
- Screenshots of the English page with arrows drawn on them
How it works
Step 1
Share the link as usual
Nothing to set up. Every install link and channel link has the languages built in.
Step 2
The phone picks the language
Hindi, Urdu, Bengali, Indonesian, Spanish, Arabic, Chinese, Portuguese, French, Turkish, Vietnamese or Russian when the phone uses it, English otherwise. Any Chinese phone gets Simplified Chinese and any Portuguese phone gets Brazilian Portuguese.
Step 3
Testers can switch
A language menu sits at the bottom of the page. Urdu and Arabic read right to left.
What is translated
The install button and steps, the notes about devices and Google Play copies, the password and private build forms, build details, release note headings, the channel page and the page footer. Your app name and release notes stay as you wrote them.
Tester emails in the same language
Invites, new build notices, reminders, "email me a link" and the device onboarding "build ready" email go out in the tester's language too, with right to left layout for Urdu and Arabic.
You can pick the language per tester when you add or edit them. Left on Auto, it follows the language their phone showed the install page in, and English until they first open a link.
Good to know
- Messages written by AppForShare's servers, such as a refused build, are still in English.
- Your dashboard and the emails to your workspace are in English.
Questions
- Can I pick the language for my testers?
- Add ?lang=ur (or hi, bn, id, es, ar, zh-Hans, pt-BR, fr, tr, vi, ru, en) to the link. Otherwise the phone's language decides, and the tester can change it at the bottom of the page.
- Are tester emails translated?
- Yes. Pick a language per tester on the Testers page, or leave it on Auto and the emails follow the language their phone showed the install page in.
- Does it cost extra?
- No. It is on every plan, and on links uploaded without an account too.
Read next
Try it on your own app
Free account in a minute. Pro starts with a 7 day free trial.
More features
- Builds on GitHub Actions
- Flutter builds on GitHub Actions
- Flutter facts and checks
- Security scan on every build
- Connect Expo (EAS builds)
- Connect Codemagic
- Send store builds to TestFlight and Google Play
- TestFlight groups and beta review on send
- TestFlight feedback in your inbox
- iOS device registration
- Hands free device setup
- Store listing editor
- App Store submission
- Google Play releases
- TestFlight tester sync
- Tester app with notifications
- Tester groups and status
- Join links for testers
- Beta and Live channels
- Build history page
- Tasks and activity feed
- Feedback to Linear and Jira
- Release checklist, approvals and blockers
- Release page per version
- Install link controls
- Several links per build
- Retire a test build
- TestFlight and APK in one link
- In-app update check
- .aab uploads
- MCP server for AI tools
- Tester feedback with screenshots
- In-app feedback link
- AI test plan for each build
- Diawi compatible upload API
- Remember my iPhone
- Install help and why it failed
- Email the install link
- Custom channel address
- Verified publisher
- Daily install email
- Zipped .app upload
- Manage link for guest uploads
- Test accounts on the install page
- Telegram notifications
- Permissions in plain words
- Reply to testers and star ratings
- Follow a channel by email
- Download button for a README
- Store pages
- Check a build before upload
- Token scopes and CLI tools
- Upload from Claude or ChatGPT
- Passkeys and email code sign in
- Free build tools
- How reports work
- Malware check on every upload
- AppForShare Android store
- Re-sign iOS builds
- Single sign on (SAML and OpenID Connect)
- Require two step sign in
- Send to Microsoft Intune
- Choose where build files are stored
- Mac and Windows builds
- Workspace address
- Automatic clean up of old builds
- Tester email from your own mail server
- Webex notifications