3 easy steps to localising your App with us

We’re well-versed in localising Android and iOS Apps. Here’s how to get it done, professionally and timeously.

  1. Send us your application files

We mostly work with .strings or .xml files for App localisation. Send us your files or simply upload to our Localisation platform using the API, cli-tool or simply e-mail them to us. Tell us which regions you’d like to target, or languages you’d like to localise into, and we’ll upload your files in order to ascertain a word count requiring localisation.

  1. We’ll send you a quotation and estimated turnaround time

Once we have your word count, we’ll send through a quotation for the requirement. The turnaround time would depend on the technicality of the text, the volume, the languages required, the subject matter itself, as well as your deadline of course.

Once you’ve decided that you like what you see, sign the quotation and send it back to us. We’ll get going right away.

  1. We’ll send you your completely localised application files to upload to your system

Our world-class localisation platform allows us to translate and export your localised iOS or Android files in exactly the same format we received them, meaning less room for error and no dreaded ‘copy and paste’ for your developers. Our system also hides your code or tags, keeping them completely insulated from the linguists. Your translation integrates seamlessly back into your system without the added risk of corrupted tags or code, and without the copy and paste nightmare most developers know causes insomnia.

Should you wish to see this in action, send us your .xml or. strings files, we’ll upload them, send you a quote, and send you back a ‘faux’ translation for you to check the integration on your side. From there, we’ll quote you, just send us a signed quote and we can unleash our tried-and-tested linguists onto your App files and take it from local App to international go-to.

NB: Should you make any updates to your App, simply send us the updated files, and via Translation Memory, we’ll be able to synchronise your previous translation with the latest requirements and keep the update costs down to a minimum. You shouldn’t have to translate the exact same string more than once, should you? This also keeps consistency within your terminology usage and prevents quality being compromised by new linguists working on your requirements.

 

Leave a Reply

Your email address will not be published. Required fields are marked *