App localization · Global mobile experiences

App localization for every screen and market.

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.

iOS and Android Store listings Interface context and length limits
Illustrative interface preview
9:41●●●
Welcome / English

Everything starts here.

Bring your next project into focus.

Email address
Get started →
9:41●●●
Bienvenida / Español

Todo comienza aquí.

Haz realidad tu próximo proyecto.

Correo electrónico
Empezar →
InicioProyectosCuenta
Language + UX context
Mobile interfaceButtons, tabs, settings and in-app messaging
OnboardingWelcome flows, account setup and permissions
App storesListing copy, screenshots and release notes
NotificationsPush alerts, reminders and confirmations
What we localize

From first tap to daily use.

App localization is about more than replacing strings. It makes every step feel clear and familiar to users in each target market.

01 / NAVIGATION

Interface strings

Buttons, navigation, tabs, settings, menus, forms, tooltips, labels and empty states across the app.

02 / ACTIVATION

Onboarding and accounts

Welcome screens, permissions, sign-up flows, verification prompts and account setup instructions.

03 / RETENTION

Push notifications

Alerts, reminders, account updates, status messages and transactional notifications.

04 / DISCOVERY

App-store listings

App titles, subtitles, descriptions, screenshot text, what's new copy and release notes.

05 / SUPPORT

Help and guidance

In-app help, knowledge-base content, setup instructions and support resources.

06 / PRODUCT

Feature terminology

Plan names, recurring features and product-specific wording maintained across screens and updates.

Mobile-first thinking

Right for the language.
Right for the screen.

Small screens amplify translation problems. Context, character lengths and system behavior need to be part of the localization brief rather than an afterthought.

01 / CONTEXT

Screen-aware wording

A short string should reflect what happens when users tap or interact with it.

02 / LENGTH

Character constraints

Labels and notifications may need adaptation to fit real device and store limits.

03 / TOKENS

Protected placeholders

Variables, names, numbers and parameters are identified separately from translatable text.

04 / CONSISTENCY

Stable feature names

Recurring terminology stays consistent across in-app text, notifications and listings.

Content and formats

Built around your app files.

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 ↗
STRINGS

Interface exports, string tables, resource files and identifiers.

JSON / XML

Structured values with keys, variables, tags and contextual metadata.

CSV / XLSX

Spreadsheet-based string exports, review columns and terminology lists.

XLIFF

Segmented exchange files and structured localization content.

STORE

App-store descriptions, screenshot captions and release communications.

Release workflow

A clear path from source copy to new markets.

Keep the source strings, store content and product language aligned throughout the release.

01 / SHARE

Send app content

Provide source strings, store copy, screenshots, target markets and delivery deadlines.

02 / REVIEW

Confirm constraints

Identify character limits, technical tokens, terminology and required output formats.

03 / LOCALIZE

Adapt the language

Work from the agreed context and terminology for each relevant screen and text type.

04 / DELIVER

Return the files

Receive the agreed localization deliverables for your product team's review and testing.

Project checklist

The best app brief includes the screens.

A screenshot can explain more than a single exported word. Send the content and the context together so the project can be scoped correctly.

Include when available

Source files or strings Target languages Target markets Screenshots / screen IDs App-store copy Notification text Character limits Placeholders / variables Release deadline Glossary / style guide
Indicative rates

The right workflow for your app content.

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.

Selected content

AI-supported + human review

£0.08 from / word

For suitable app-content batches where an AI-supported workflow with human review fits the material and requirements.

Check project suitability
Specialist requirements

Complex or specialist

£0.16 from / word

For terminology-heavy or technically demanding releases requiring further specialist attention and review.

Discuss a complex release
Common questions

Everything you need to know before 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
What is app localization?

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.

Do you localize both iOS and Android apps?

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.

Can you localize App Store and Google Play listings?

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.

Can you work with JSON, XLIFF and string exports?

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.

What is the difference between app and software localization?

App localization focuses on mobile screens, onboarding, notifications and app-store content. Software localization also covers broader SaaS, desktop and web product interfaces.

How much does app localization cost?

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.

What should I send for a project quote?

Send source strings, target languages, relevant screenshots or screen IDs, app-store content, a release deadline and any terminology or character-limit guidance.

Your next market starts here

Make every tap feel local.

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.