Traditional Translation Workflow vs. Automation with doloc

In the traditional workflow, translations are handled by third parties and not by developers themselves. These third parties could be agencies, in-house services, or individual translators, which can result in bottlenecks and support delays.

By contrast, instead of a separate translation step, the extracted XLIFF files can be 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).

Traditional Workflow

1. Extraction: The developer extracts the app’s text into translation files (e.g., XLIFF).
2. Handover: The extracted files are handed over to the translator, usually in batches. This 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 takes 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 and adds manual effort to the process.
   Localization delays and manual, error-prone steps

Workflow with Automated Translations

1. Extraction and Translation: The developer extracts the text into (for example) 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 validate automated translations afterward or asynchronously. XLIFF includes specific states (e.g., “translated,” “final”) to mark reviewed segments.
   Continuous localization and integrated testing

Summary

With the traditional workflow, there are localization delays. Typically, there is a period of two weeks or more where the app isn’t fully localized. This can block releases or degrade the user experience for non-default languages. Additionally, the manual handover and integration steps increase costs and the likelihood of errors.

With the automated translation workflow, doloc streamlines this process significantly. Translations are always up to date, ensuring a fully localized experience for users across languages. Localized texts can be included in your acceptance tests, helping you catch potential issues early and maintain overall quality.