Streamline app localization with doloc

In this post, I'll outline an optimized translation workflow for app localization¹. This approach applies to both web and native applications (iOS, Android, Windows, etc.), with just one prerequisite: using XLIFF (1.2 or 2.0) for your translation files. XLIFF is widely supported across localization tools, making it a practical choice for most teams.

The proposed setup can dramatically reduce time-to-market and lower translation costs.

The Traditional Workflow

To understand where bottlenecks and delays arise, let’s take a quick look at the traditional localization workflow:

Typically, translations are handled by third parties rather than developers themselves. This might be an agency, an in-house service, or another individual we’ll refer to as the "translator."

1. Extraction: The developer extracts the app's text into translation files (XLIFF).

2. Handover: The extracted files are handed over to the translator, usually in batches. This batching contributes significantly to delays; for example, new texts may only be sent for translation every two weeks.

3. Translation: The translator works on these files, translating new or updated text and striving to maintain language consistency. This step, often taking 1-3 days, requires effort and is prone to errors, particularly in larger apps with limited tooling support.

4. Integration: Once translations are complete, the files are handed back to the developer to integrate into the codebase. With the delay, this can involve resolving complex conflicts, adding manual effort to the process.

In summary:

• Localization Delays: Typically, there’s a period of two weeks or more where the app isn’t fully localized, which can block releases or degrade the user experience for non-default languages.
• Manual and Error-Prone Steps: The manual handover and integration steps increase costs and the likelihood of errors.

A Leaner Workflow with Automated Translations

By integrating doloc into the extraction process, you can streamline this workflow significantly. Here’s how it works:

Instead of a separate translation step, the extracted XLIFF files are sent to doloc automatically (via a simple curl command - see getting started. Doloc immediately translates the content and returns the updated files. The entire process boils down to just one step (plus an optional QA step):

1. Extraction and Translation: The developer extracts the text into XLIFF files, and doloc instantly translates them. The files are updated right away, so translations are available from the start.

2. Optional: Quality Assurance (QA): If desired, a translator can quickly validate automated translations. XLIFF includes specific states (e.g., "translated," "final") to mark reviewed segments.

This automated setup means QA efforts are minimal, and releases are no longer delayed by translation. Since your app is always localized, you may even find yourself reducing QA cycles as you gain confidence in the quality of doloc’s translations.

Additional Benefits:

• Continuous Localization: Translations are always up to date, ensuring a fully localized experience for users across languages.
• Integrated Testing: Localized text can be included in your acceptance tests, helping you catch potential issues early and maintain overall quality.

We Value Your Feedback

Disclaimer: I am the founder of doloc.

We're always working to improve. If you've tried doloc (we offer a free 14-day trial!) or if you have thoughts on whether it might fit into your workflow, we’d love to hear from you. Drop a comment below!

1. Localization includes more than just translation, but since other aspects are often centrally controlled or configured, we focus here on translation as the primary challenge. ↩