Mobile Application Localization to Russian Language
Adding Russian language to already finished application — task that looks simpler than it actually is. Technical strings in strings.xml or Localizable.strings translated in a day. Problems start where strings are not just strings: numerals ("1 notification", "3 notifications", "5 notifications"), cases when substituting names, long words that break UI, or RTL-neutral layout that stops working.
Plurals and Cases — Main Complexity of Russian
Russian language has six plural forms for nouns depending on number. Android supports this natively through <plurals> in strings.xml:
<plurals name="notification_count">
<item quantity="one">%d notification</item>
<item quantity="few">%d notifications</item>
<item quantity="many">%d notifications</item>
<item quantity="other">%d notifications</item>
</plurals>
In code: resources.getQuantityString(R.plurals.notification_count, count, count).
On iOS — String(localized:) with .init(format:) and NSLocalizedString support CLDR plural rules through .stringsdict. Format .stringsdict XML-heavy, but works correctly with NSLocalizedString("notification_count", comment: "") + stringsdict file.
In React Native: i18n-js or react-i18next with returnObjects: true for plural forms. Without explicit library support — write helper manually.
Substitution with agreement ("Hello, %@" → "Hello, Ivan") — here named placeholders enough. Problem arises when agreement needed: "Ivan's order" vs "Marina's order" — ending different. For such cases either rephrase without agreement, or add separate keys for different forms.
String Length and UI
Russian words on average 20–40% longer than English equivalents. "Settings" → "Настройки" — normal. "Notifications" → "Уведомления" — longer. "Privacy Policy" → "Политика конфиденциальности" — almost twice. Fixed button width, truncation instead of wrap, hardcoded icon offsets — all this breaks on localization.
Check UI in pseudo-localization during development: аccoutability → [аccoutàbïlïтý~~] — reveals problem areas before translation. Xcode supports Pseudo-localization in scheme (Application Language: Double-Length Pseudolanguage).
Keyboard and Input
For Russian input fields: keyboardType and returnKeyType don't change, but autocapitalizationType worth checking — Russian autocapitalization sometimes behaves differently than expected. spellCheckingType with Russian dictionary available on iOS and Android system-wise, enabled automatically when language selected.
Process
Audit existing strings → export to XLIFF (iOS) or Android String Resources → translation + plural check → import → testing on device with Russian locale → UI overflow check. Separately check date and number formats: DateFormatter and NumberFormatter with Locale(identifier: "ru_RU") give "26 марта 2026" and "1 234,56" instead of "03/26/2026" and "1,234.56".
Timeframe: two to four working days for application with 200–500 strings, including UI testing.