Comparison of Traditional Workflow vs. Workflow with Automated Translations

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 other individual translators what can result into bottlenecks and support delays.

On the other side, 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 (XLIFF).
2. Handover: The extracted files are handed over ro the translator, usually in batches. Thes contributes significantly to delay: 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 taken 1-3 days, requires effort and ist prone to errors, particularly in larger apps with limited tooling support.
4. Integration: One translations are complete, the files are handed back to the developer to integrate into the codebase. With the delay, this can incolce resolving complex conflicts and adding manual effort to the process.
   Localization Delays AND Manual and Error-Prone Steps

Workflow with Automated Translations

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.
   Continuous Localization AND Integrated Testing

Summary

With the Traditional Workflow, there are localization delays. Typically there is a periode 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. Additionaly, the manual handover and integration steps increase costs and the likelihood of errors.

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