All posts

Test your app in other languages before launch

· 7 min read

Translated apps break in the same few ways. A German button label is twice as long as the English one and gets cut off. A screen you forgot still says English. A price shows up as 1.234,56 where the user expects something else. An Arabic user opens your app and the layout is still pointing the wrong way. I checked the vendor docs for this post in November 2026, and every quote below comes from an official page I opened that month.

Short answer: before you ship a translation, run your app once in a pseudolanguage (Xcode and Android both have them), once in a real right-to-left language, and once with real dates, prices and plurals. Then ask testers who speak the language to walk through every main screen. Pseudolanguages find layout problems. Only a person who speaks the language can tell you if the words are right.

iOS: run Xcode with a pseudolanguage

Apple's Preparing your interface for localization page says to choose Product > Scheme > Edit Scheme, select the Run action, click Options, and pick "one of the pseudolanguages at the bottom of the App Language pop-up menu". Those names are in the table on that page. Three of them cover most of what you need:

  • Double-Length Pseudolanguage. The page says it "Doubles the length of localizable strings to test whether views adjust their size and position." This is your cut-off text test.
  • Right-to-Left Pseudolanguage. It "Simulates a right-to-left writing direction to test whether views flip accordingly." You do not need to read Arabic to see if the screen mirrors.
  • Bounded String Pseudolanguage. It "Wraps strings to identify places where localized strings may appear truncated."

The same page also describes a switch for hard-coded text. Under Localization Debugging in the Run options, select "Show non-localized strings", and "the nonlocalized strings appear in all caps" when you run the app. Every all-caps label is a string that will never be translated. If you use SwiftUI, Apple's Previewing localizations page says to set the locale environment value in a preview, and to also set layoutDirection to rightToLeft to preview right-to-left languages.

To try a real language, Apple's Testing localizations when running your app page says to choose the language from the "App Language" pop-up menu and the region from the "App Region" pop-up menu in the same Run options.

Android: turn on the pseudolocales

Android's pseudolocales page says the platform has two. English (XA) "adds Latin accents to the base English UI text, expands the original text by adding non-accented text, and brackets each message unit". AR (XB) "sets the text direction of the original left-to-right messages to the right-to-left direction". The page adds that pseudolocales can help you make an RTL version of your app "even if you don't write or speak any RTL languages."

To enable them, add this to your debug build type in build.gradle, as the page shows:

android {
  buildTypes {
    debug {
      pseudoLocalesEnabled true
    }
  }
}

Then build and run. On Android 5.0 (API level 21) or higher, the page says to open Settings, tap Languages and input, then Language preferences, and drag a pseudolocale to the top of the list. It says you need Android 4.3 (API level 18) or higher, with developer options on.

The page lists what this catches: hard-coded strings "display as unaccented text", layout breakage from text expansion, string concatenation shown as one message split into several brackets, and right-to-left problems such as elements not being mirrored.

For plurals, the string resources page says the full set of quantity types Android supports is "zero, one, two, few, many, and other", and that you should "always supply" the one and other strings. Your translators know which ones their language needs. On layout, Android's language and culture page says to "Convert left and right to start and end" in your layout files, and to set android:supportsRtl="true" in the manifest. Its test advice is to use developer options "and invite people who use RTL scripts to use your app."

Flutter and Expo

Flutter's internationalization page says the flutter_localizations widgets delegate "defines the default text direction, either left-to-right or right-to-left", and suggests switching the platform's locale to Spanish to see the messages change. Expo's localization guide says RTL support is enabled by default in SDK 58 and later, and that "You can force the RTL layout for testing" with the forcesRTL option of the expo-localization plugin. I did not find a pseudolocale mentioned on either page, so for those apps I would run the Android and iOS tools above on the built app.

Web apps

For formats, let the browser do the work. MDN says Intl.DateTimeFormat "enables language-sensitive date and time formatting" and Intl.NumberFormat "enables language-sensitive number formatting". Its NumberFormat example formats 123456.789 for Germany as a euro amount and gets "123.456,79 €". For plurals, MDN says Intl.PluralRules "enables plural-sensitive formatting and plural-related language rules".

For direction, MDN's dir attribute page says to set dir="rtl" on the <html> element when the page is mostly in a right-to-left script such as Arabic or Hebrew. It also says "The lang attribute declares the language, but does not imply the base direction." So you need both. For user-typed text, it says the auto value "should be used for data with an unknown directionality".

To check long words, switch your test browser to German or Dutch and open the screens with the longest labels.

Dates, numbers, currency and plurals

These bugs hide because the app still "works". 03/04 can mean 3 April or 4 March. 1.234,56 is a normal number in many countries. "1 items" is what you get when you add an "s" in code. Apple's formatters page says "Some languages use the period (.) as a decimal separator, and others use the comma (,)", and tells you to use the formatters built into Foundation instead of handling the variations yourself. Apple's string catalog page says "Languages have different grammatical rules for handling plurals of nouns and units", and describes a "Vary by Plural" option in the string catalog editor. Use those APIs, not hand-built strings, and test one screen with the number 1, the number 2 and a large number.

Store listings are separate

Your store text and screenshots do not translate when your app does. Apple's Localize app information page says that when you add a language, screenshots and properties "default to those of the primary language, except for the description and keywords". On Google Play, the Translate and localize your app page says you can add translations for your "app's store listing page, app strings or in-app products", and the steps start from Store listing, then Manage translations. For the listing basics, see the App Store product page for a first app.

A test plan testers can follow

You can paste this into your test task. For how to write the rest of the task, see how to write a test task.

Please set your phone to [language] and open the app.
1. Open every main screen.
2. Note any English text that is left over.
3. Note text that is cut off, overlaps, or does not fit in its button.
4. Check dates, prices and numbers: do they look right for your country?
5. Right-to-left languages only: does the layout mirror, and do
   back arrows and other pointing icons flip?
6. Tell me if any wording sounds odd or wrong to a native speaker.
Please say which phone and language you used.

Ask for testers who speak the language, and say why: you want to know about meaning, not only layout. A pseudolanguage cannot tell you that a button says something rude. For the phone side, see testing on phones you don't own. Apple's Localization page says the same: to get the best feedback, distribute your app "to native speakers in the languages that you support".

Where TestSwap fits

TestSwap is a free app testing exchange where indie developers test each other's apps. You post a web, iOS or Android app with a link testers can open or install, like a TestFlight link or a Google Play testing link. You can add a test login that only signed-in testers see. Everyone starts with 3 credits. Writing a review earns 1, and each review your app receives costs 1. The maker can rate each review 👍 or 👎, and a 👎 takes back the credit the reviewer earned.

Put the language in your test task, like "please test with your phone set to Spanish". I can't promise how many testers speak a given language, so ask for it in the task and see who answers. TestSwap is not affiliated with Apple or Google.

The checklist

  1. Run the app in a pseudolanguage (Double-Length on iOS, English (XA) on Android) and fix cut-off text.
  2. Turn on "Show non-localized strings" in Xcode, and look for unaccented text in the Android pseudolocale. Fix every hard-coded string.
  3. Run the right-to-left pseudolanguage (or AR (XB)) and check the layout mirrors.
  4. Use start and end instead of left and right on Android, and dir on the web.
  5. Format dates, numbers and currency with the platform tools, not by hand.
  6. Use plural resources, and test the numbers 1, 2 and a large one.
  7. Translate the store text and screenshots too.
  8. Put the test plan in your task and ask for native speakers.

Try it on your own app first. Then post it on TestSwap and tell me what's missing or wrong (@dizid on X).