Mobile App Localization to Russian: Complete Guide

You've integrated string translation via strings.xml or Localizable.strings — and everything works in English. But when it comes to Russian, surprises start. Numerals: '1 notification', '3 notifications', '5 notifications' — standard pluralization requires four forms. Cases: 'Ivan's order' vs 'Marina's order'. Long words: 'Политика конфиденциальности' instead of 'Privacy Policy'. And RTL-neutral layout starts behaving unpredictably. Recently, a fintech client encountered the 'Submit' button turning into 'Отправить' and overflowing the screen on iPhone SE after localization. We solved this in two days using auto layout and dynamic height. We are a team of mobile developers with 10+ years of experience — we solve such tasks turnkey, guaranteeing correct localization to Russian. We are certified by Apple and Google, with over 15 projects featuring Russian localization. We'll evaluate your project for free.

How to Properly Handle Pluralization in Android and iOS?

Russian uses six plural forms for nouns depending on the number. Android supports this natively via <plurals> in strings.xml:

<plurals name="notification_count">
    <item quantity="one">%d уведомление</item>
    <item quantity="few">%d уведомления</item>
    <item quantity="many">%d уведомлений</item>
    <item quantity="other">%d уведомления</item>
</plurals>

In code: resources.getQuantityString(R.plurals.notification_count, count, count).

iOS uses String(localized:) with .init(format:) and NSLocalizedString, which support CLDR plural rules via .stringsdict. The .stringsdict format is more verbose but works correctly with NSString.localizedStringWithFormat. In React Native, i18n-js or react-i18next with returnObjects: true are used. Without explicit plural support, you need to write a helper manually. The native pluralization mechanism (Android <plurals> / iOS .stringsdict) is 2 times more accurate than custom solutions, especially for numbers 21, 31, etc.

Substitution with agreement ("Hello, %@" → "Hello, Ivan") is simple with named placeholders. The problem arises with agreement: "Ivan's order" vs "Marina's order" — different endings. For such cases, either rephrase the string without agreement or add separate keys for different forms.

Why Does Russian Text Break the UI?

Russian words are on average 20–40% longer than their English equivalents. "Settings" → "Настройки" — fine. "Notifications" → "Уведомления" — longer. "Privacy Policy" → "Политика конфиденциальности" — almost double. Fixed button widths, truncation instead of wrap, icons with hardcoded offsets — all break during localization. We check the UI using pseudolocalization during development: аccoutability → [аccoutàbïlïтý~~] — highlights problem areas before translation. Xcode supports Pseudolocalization in schemes (Application Language: Double-Length Pseudolanguage). This saves up to 50% of time on layout fixes.

What About Keyboard and Input?

For Russian input fields: keyboardType and returnKeyType remain unchanged, but check autocapitalizationType — Russian autocapitalization sometimes behaves differently. spellCheckingType with Russian dictionary is available system-wide on iOS and Android, activated automatically when selecting the language.

Comparison of Pluralization Approaches

Among the three, Android and iOS provide built-in support for Russian rules, while React Native requires an additional library. For large projects, we recommend native solutions.

What's Included in Russian Localization?

Total duration — from 2 to 4 business days for an app with 200–500 strings. We export strings using XLIFF format, supported by all major platforms. When publishing to the App Store, be sure to comply with section 5.1 of the App Store Review Guidelines regarding localization.

How We Guarantee Quality?

We use automated testing with XCTest/Espresso on pseudolocalized UI, check plurals at boundary values (0, 1, 2, 3, 10, 21, 100). For iOS — .stringsdict is mandatory, for Android — <plurals> with correct quantity. Our experience: over 15 projects, certified specialists. According to Apple documentation, using .stringsdict is critical for correct pluralization. Get a consultation — we'll evaluate your project for free and suggest an optimal plan.

Typical Mistakes in Russian Localization

• Ignoring stringsdict/plurals — leads to errors like "1 уведомления". Always use system mechanisms.
• Fixed button widths — use wrap_content (Android) or sizeThatFits (iOS) for Russian.
• Incorrect date formats — DateFormatter with ru_RU gives "March 26, 2026", not "03/26/2026".
• Forgotten system strings — Cancel, OK, Save — localize them via NSLocalizedString or strings.xml.
• Links to third-party services — if the app contains web views or "Call" buttons, check that Russian is supported.

What's Next?

Contact us for a consultation: we will offer the optimal solution for your project. Get a preliminary estimate of timeline and budget within one day.

Mobile App Localization: i18n, RTL, Dynamic Language Switching

When localizing apps, we often encounter non-obvious errors: date 04/05 for an American is April 5, for a European it is May 4. Amount "1,000.50" in most countries is one thousand and a half, in Germany it is one and fifty cents. The number of words for "1 file", "3 files", "5 files" in Russian has three different forms; Arabic has six plural forms. If the app architecture does not account for this from the start, localization turns into a series of patches. Our 7-year experience in mobile development and 50+ releases on App Store and Google Play confirm: proper i18n/l10n from the first commit pays off many times over.

How to Set Up Basic Localization Infrastructure?

iOS: From Localizable.strings to String Catalogs

Historically, strings in iOS were stored in Localizable.strings — a simple key=value format. With Xcode 15, String Catalogs (.xcstrings) emerged — a JSON-based format that stores all locales in one file, displays translation status (translated/outdated/missing), and is integrated with the Xcode UI.

String(localized: "welcome_title") in Swift 5.7+ replaces NSLocalizedString(...). Shorter, type-safe. String Interpolation in localized strings: String(localized: "items_count \(count)") with a pluralization rule in .xcstrings — the system automatically selects the correct form for the language. Pluralization via .stringsdict (old approach) or directly in String Catalog with NSStringPluralRuleType. For Russian, you need to define forms one (1 file), few (3 files), many (5 files), other (fallback). Skipping few for Russian means getting "5 files" where it should be "3 files". String Catalogs cut setup time by half compared to .stringsdict.

Android: XML Resources and String Formats

res/values/strings.xml for base locale (en), res/values-ru/strings.xml for Russian. Plural strings via <plurals> with <item quantity="one">, <item quantity="few">, <item quantity="many">. resources.getQuantityString(R.plurals.file_count, count, count) — the first count selects the form, the second is substituted into the string.

In Compose: stringResource(R.string.key) and pluralStringResource(R.plurals.file_count, count, count). A type-safe alternative is the Lyricist library, which generates typed strings from annotations.

Android App Bundle with android:splitByLocale="true" in bundle.gradle — resources are delivered only for device languages. APK size reduces by 15-20%, resources of needed locales are loaded on demand via Play Asset Delivery. Important: on Android 8+ Configuration.locales is a list, not a single language.

Flutter: intl and Abstraction Layers

Flutter intl package is the standard. AppLocalizations.of(context).welcomeTitle is generated from ARB files (app_en.arb, app_ru.arb). flutter gen-l10n generates typed code. Pluralization via {count, plural, one{# file} few{# files} many{# files} other{# files}} in ARB.

For large apps with 50+ languages — easy_localization with support for YAML/JSON/CSV formats and lazy loading of translations: not all 50 languages load at once, only the needed one. This reduces initial load size by 30%.

Comparison Table of Approaches

How to Implement RTL Support Without Rewriting UI?

Arabic, Hebrew, Persian, Urdu are RTL (Right-to-Left) languages. This changes not only text direction but the entire UI layout: back button on the right, icons mirrored, padding and margins inverted.

On iOS, everything is done via semanticContentAttribute and Auto Layout. Layout constraints with leading/trailing (not left/right) automatically invert for RTL. UIView.semanticContentAttribute = .forceRightToLeft for a specific component. System components (UINavigationController, UITableView, UIStackView) switch automatically when RTL locale is set. Problems arise with custom UI where the developer hardcoded left/right constraints or used frame-based layout. In such cases, we rewrite custom views to Auto Layout — it takes 1-2 days per screen.

On Android, android:supportsRtl="true" in AndroidManifest enables RTL support. Use start/end instead of left/right in XML attributes: paddingStart, layout_marginEnd, textAlignment="viewStart". Use LayoutInflater with android:layoutDirection="rtl" for preview. Directional icons (arrows, chevron) need to be mirrored — android:autoMirrored="true" in drawable for automatic inversion with RTL.

On Flutter, Directionality widget with TextDirection.rtl controls direction for the subtree. Use Padding(EdgeInsetsDirectional.fromSTEB(...)) instead of EdgeInsets.only(left:...). Row automatically respects TextDirection from Directionality. Most Material widgets are RTL-ready, but custom CustomPainter is not: you need to get TextDirection from context and account for it manually.

Testing RTL: on iOS, go to Settings → General → Language & Region → Region: Saudi Arabia to switch to RTL mode without changing system language. On Android, adb shell setprop debug.force.rtl 1 forces RTL for debugging. This catches up to 80% of RTL issues before release.

Why Is Dynamic Language Switching a Bottleneck?

Switching language without restarting the app is non-trivial, especially if the system is built on system locale. We identified three main approaches.

iOS does not natively support changing the app language without restarting. The cleanest approach is to store the selected language in UserDefaults, create a Bundle with the required localization at launch, and use a custom NSLocalizedString through this Bundle. Bundle.setLanguage("ru") via swizzling Bundle.localizedString(forKey:value:table:) works but uses runtime swizzling, which is not ideal. Alternative: a custom string system on top of NSBundle that rereads files when the language changes. On switch, recreate the root ViewController.

Android with API 33: LocaleManager.setApplicationLocales() — official API for changing app language without system restart, without Activity recreation if using AppCompatDelegate.setApplicationLocales(). Below API 33 — Configuration.setLocale() + recreate() for Activity. When changing language, notify all open Activities via broadcast or ViewModel. For Android 12+, we also use android:localeConfig in the manifest — this allows the system to know supported languages without additional configuration.

Flutter — the simplest of the three. LocalizationsDelegate reloads when the locale in MaterialApp changes. Store the selected language in a provider (Riverpod/Provider/Bloc), changing locale in MaterialApp rebuilds the tree with new strings. Virtually no boilerplate when using easy_localization. However, there is a nuance: all StatefulWidgets that do not subscribe to locale changes will not update — you need to explicitly pass locale via InheritedWidget or rebuild the tree.

How to Format Dates, Numbers, and Currencies?

DateFormatter (iOS) and DateFormat (Android, intl) — always with explicit locale, never without. DateFormatter().dateStyle = .medium with locale = Locale(identifier: "ru_RU") gives "4 мая", with Locale(identifier: "en_US") gives "May 4". We use RelativeDateTimeFormatter (iOS 13+) and RelativeTimeFormatter via the intl package — don't reinvent the wheel with manual formatting.

NumberFormatter / NumberFormat.currency() for currencies. Currency symbol, thousand and decimal separators are all locale-specific. Hardcoding "₽" or "." as separator is an error. Locale(identifier: "ru_RU") + NumberFormatter.numberStyle = .currency with currencyCode = "RUB" gives correct formatting automatically.

What Are Typical Localization Mistakes?

String concatenation instead of formatting: "Hello, " + name + "!" works for SVO languages, but in Japanese the name comes before the greeting. String(format: "greeting %@", name) with greeting = "%@ さん、こんにちは" in the Japanese file is correct. Fixed UI size for text: German is on average 30% longer than English. Use AutoLayout with proper constraints, adjustsFontSizeToFitWidth where acceptable, dynamic cell height via UITableView.automaticDimension. Images with embedded text require localized versions or replacement with text overlay.

Work Process: How We Localize an App Turnkey

1. Analysis and audit (2-5 days) — code review for i18n readiness, identify hardcoded strings, assess RTL complexity, prepare screen map.
2. Architecture design (3-7 days) — choose stack (String Catalogs/ARB/XML), set up automation pipelines (Crowdin/Lokalise), create base strings.
3. Implementation (1-4 weeks depending on scope) — integrate i18n, pluralization, RTL, formatting. In parallel, translate content.
4. Testing (3-7 days) — functional (language switch, RTL, number display), linguistic (LQA), screenshot testing (localized store screenshots).
5. Deployment and monitoring (1-2 days) — publish to stores, set up analytics (events on languages), user feedback collection.

Deliverables

• Source code with full i18n infrastructure
• Documentation on adding a new language (playbook)
• Translation files (ARB/XML/xcstrings) + glossary
• Automation: CI/CD integration with translation services
• Access to repository with full revision history
• Training for the client's team (1-2 sessions)
• Code warranty — 6 months, free localization bug fixes

Timeline and Cost

Pricing is customized based on project scope. Contact us for a detailed estimate. On average, automation achieves 40% budget savings. We offer a free project assessment — get in touch for a quote and project plan.

Why Choose Us

We are certified developers (Apple WWDC Scholarship, Google Associate Android Developer). Over 5 years in the market, we have completed 50+ localization projects, including apps for 15 languages with RTL. We guarantee compliance with App Store Review Guidelines (Section 4.2/5.1) and Google Play Policies (User Data). Our clients report an average of 40% reduction in time-to-market for new regions thanks to translation automation and thoughtful architecture.

Additional information on internationalization and localization can be found on Wikipedia and the RTL specification.

Get a consultation for your project — leave a request on our website, we will prepare a detailed plan and timeline. Order a localization audit of your app: the first phase reveals up to 80% of bottlenecks with no implementation cost.