Mobile App Localization Framework

You are a mobile localization engineer who has managed the internationalization and localization of applications serving users in dozens of languages and regions. Create a comprehensive localization framework for the following mobile application.

App Details:
App Name: [APP NAME]
Current Languages: [LIST CURRENT LANGUAGES]
Target Languages: [LIST NEW TARGET LANGUAGES]
Content Types: [UI STRINGS/DYNAMIC CONTENT/MEDIA/LEGAL]
RTL Language Support Needed: [YES/NO]
Localization Budget: [PER-LANGUAGE BUDGET]
Translation Approach: [PROFESSIONAL/CROWDSOURCED/AI-ASSISTED/HYBRID]

Section 1 - Internationalization Architecture:
Define the string externalization strategy ensuring all user-facing text is extracted into resource files using Localizable.strings or String Catalogs on iOS and strings.xml on Android or the appropriate framework-specific approach. Specify the string key naming convention using a hierarchical format such as screen_component_purpose that scales as the app grows and prevents key collisions. Create the pluralization and gender handling approach using the platform plural rules on Android and stringsdict on iOS that correctly handle the plural categories required by each target language. Design the number, date, currency, and measurement formatting strategy using platform locale APIs rather than hardcoded formats. Address the string interpolation approach that allows translators to reorder parameters for languages with different word order using positional format specifiers.

Section 2 - Layout Adaptation and RTL Support:
Define the flexible layout strategy using constraint-based layouts and auto layout that accommodate text expansion up to two hundred percent for languages like German and Finnish compared to English. Specify the right-to-left layout implementation including mirroring navigation flows, reversing horizontal scroll directions, and flipping directional icons while preserving elements that should not mirror such as media playback controls and phone numbers. Create the font management approach for languages requiring different font families including CJK languages, Arabic, Thai, and Devanagari with appropriate fallback chains. Design the dynamic type integration ensuring localized text respects system text size preferences across all languages. Address the image and icon localization strategy identifying which visual assets contain text or culturally specific imagery that needs localization and creating the asset variant management approach.

Section 3 - Translation Workflow and Tools:
Define the translation management system selection comparing tools like Lokalise, Phrase, Crowdin, or Transifex based on mobile platform integration, API capabilities, and collaboration features. Specify the translation workflow from string creation through translation, review, and integration including roles and responsibilities at each step. Create the context provision strategy for translators including screenshots, character limits, descriptions, and glossary terms that reduce translation errors. Design the continuous localization pipeline that automatically exports new strings to the translation platform when developers merge code and automatically imports completed translations back into the codebase. Address the translation memory and glossary management ensuring consistency across the application and reducing costs by reusing previously translated content.

Section 4 - Dynamic Content and Server-Side Localization:
Define the server-side localization strategy for dynamic content including API response localization, push notification content, and email templates sent from the backend. Specify the locale negotiation protocol between the mobile client and the server including how the preferred language is communicated, how fallback languages are selected, and how locale changes during a session are handled. Create the content management system integration for localized content including blog posts, help articles, legal documents, and marketing content that may update independently of app releases. Design the A/B testing approach for localized content allowing different messaging variants to be tested within specific language markets. Address the user-generated content handling including whether to translate user content, how to display mixed-language content, and how to handle language detection for content moderation.

Section 5 - Cultural Adaptation and Market Customization:
Define the cultural adaptation requirements beyond language including date formats, address formats, name ordering conventions, and color symbolism differences. Specify the market-specific feature configuration allowing different features, payment methods, or content to be available in different regions through server-driven configuration. Create the legal and regulatory compliance checklist for each target market including privacy policy translations, terms of service localization, age rating differences, and data residency requirements. Design the cultural review process for identifying and resolving cultural sensitivity issues in content, imagery, and interaction patterns before launching in new markets. Address the regional app store optimization including localized app names, descriptions, keywords, and screenshots for each target market.

Section 6 - Quality Assurance and Maintenance:
Define the localization QA process including linguistic review by native speakers, functional testing in each language, and visual inspection for layout issues caused by text length variations. Specify the pseudo-localization testing approach using artificially expanded and accented strings during development to identify internationalization issues before real translations are available. Create the automated localization checks integrated into the CI pipeline including missing translation detection, string length validation, placeholder consistency verification, and screenshot generation for all supported languages. Design the localization metrics dashboard tracking translation coverage, missing string rates, translation turnaround time, and per-language crash rates that might indicate localization-related bugs. Address the ongoing localization maintenance process including how new features are localized, how translation corrections are handled, and how to manage the growing volume of localizable content as the app evolves.