Interface strings
Buttons, navigation, tabs, settings, menus, forms, tooltips, labels and empty states across the app.
Take your mobile app into new languages without losing the experience that makes it work. We localize iOS and Android interface text, onboarding, permission prompts, notifications and app-store listings with context, terminology and screen constraints in mind.
Bring your next project into focus.
Haz realidad tu próximo proyecto.
App localization is about more than replacing strings. It makes every step feel clear and familiar to users in each target market.
Buttons, navigation, tabs, settings, menus, forms, tooltips, labels and empty states across the app.
Welcome screens, permissions, sign-up flows, verification prompts and account setup instructions.
Alerts, reminders, account updates, status messages and transactional notifications.
App titles, subtitles, descriptions, screenshot text, what's new copy and release notes.
In-app help, knowledge-base content, setup instructions and support resources.
Plan names, recurring features and product-specific wording maintained across screens and updates.
Small screens amplify translation problems. Context, character lengths and system behavior need to be part of the localization brief rather than an afterthought.
A short string should reflect what happens when users tap or interact with it.
Labels and notifications may need adaptation to fit real device and store limits.
Variables, names, numbers and parameters are identified separately from translatable text.
Recurring terminology stays consistent across in-app text, notifications and listings.
App teams work with structured strings, content exports, screenshots and store-copy documents. We review the source material and agree on what is translatable and how it needs to be returned.
Share a sample if the export is proprietary or contains technical tokens, and we will confirm the suitable approach before work begins.
Ask about file compatibility ↗STRINGSInterface exports, string tables, resource files and identifiers.
JSON / XMLStructured values with keys, variables, tags and contextual metadata.
CSV / XLSXSpreadsheet-based string exports, review columns and terminology lists.
XLIFFSegmented exchange files and structured localization content.
STOREApp-store descriptions, screenshot captions and release communications.
Keep the source strings, store content and product language aligned throughout the release.
Provide source strings, store copy, screenshots, target markets and delivery deadlines.
Identify character limits, technical tokens, terminology and required output formats.
Work from the agreed context and terminology for each relevant screen and text type.
Receive the agreed localization deliverables for your product team's review and testing.
A screenshot can explain more than a single exported word. Send the content and the context together so the project can be scoped correctly.
The starting rates already published on this page are retained. Final pricing is confirmed after reviewing languages, volume, formats, context and deadline.
Starting rates per source word, not a fixed project price. Some content, file preparation or testing requirements may be scoped separately.
For suitable app-content batches where an AI-supported workflow with human review fits the material and requirements.
Check project suitability ↗For mobile UI, onboarding and store content needing natural product language and context-sensitive human work.
Start your app order ↗For terminology-heavy or technically demanding releases requiring further specialist attention and review.
Discuss a complex release ↗App localization is for mobile experience and store-copy needs. Other content types have their own dedicated service pages.
Web products, dashboards, desktop interfaces and resource files.
↗ Web journeysLanding pages, navigation, calls to action and multilingual search copy.
↗ CampaignsPromotional content and market-facing messaging beyond the app itself.
↗ All optionsExplore all the specialist services for a broader international launch.
↗App context changes how even a two-word button should be translated. A clear brief helps us give a more accurate answer.
Ask an app question ↗App localization adapts a mobile application's user-facing content for another language and market. It can include interface strings, onboarding, permission prompts, notifications, help content and app-store listings.
We can review source strings and related content from iOS and Android app projects. Please share the actual export format and any constraints so the scope and compatible return format can be confirmed.
App-store content can include titles, short and long descriptions, screenshots, release notes and promotional copy. Character limits and store requirements are considered as part of the brief.
Structured files and common string exports can be reviewed. Share samples, variables, screen references and non-translatable keys so the team can confirm file suitability.
App localization focuses on mobile screens, onboarding, notifications and app-store content. Software localization also covers broader SaaS, desktop and web product interfaces.
Published starting rates are £0.08 per word for suitable AI-supported work with human review, £0.12 per word for human app localization and £0.16 per word for specialist or complex work. Final quotations depend on your files and requirements.
Send source strings, target languages, relevant screenshots or screen IDs, app-store content, a release deadline and any terminology or character-limit guidance.
From the first welcome screen to the latest app update, share your content and release brief. We'll help define the appropriate localization scope and return format.