Specifics of the translation and localization of mobile applications
It is known that sales are essential to succeed in an online business. The more sales, the higher your income. Sales, registrations, downloads are at the very bottom of the conversion funnel, at the top of which is the coverage. The greater the audience coverage and the higher the number of people who see your application, the more sales you receive.
Translation into just 3 languages, namely English, Spanish and Russian, allows you to reach 1.3 billion people. To achieve maximum coverage, you should have your mobile application translated into at least 3-5 languages. It must be done so that the user does not feel it is a translation. Such a result can be achieved only if an experienced industry translator is involved, who is also a native speaker of the target language.
In Workogram, translation of mobile applications is one of the most popular areas along with website translation. It requires knowledge of the code and skills to work with special programs, so a whole team is involved in working on one project, consisting of a project manager, layout designer, programmer, translator, and editor.
In principle, translations made for iOS and Android systems are relevant now. But we take on localization of all possible systems.
We work with the following file types:
- .xml
- .plist
- .strings
- .stringsdict
- .xliff
- .json
What languages should the application be translated into?
Today, due to globalization, the localization of mobile applications has become available in a matter of days. You provide us with the source code for mobile applications, we translate and test them in many languages of the world: English, Turkish, Chinese and even Hindi. You just have to put the translation in the code and then consider yourself already in the world market. And every person, regardless of the nationality, can download localized software to one’s smartphone.
Don’t risk! Order a translation of the application with Workogram and save not only time, but also money.
Example
We received an order to localize a mobile application in Russian. As source materials, we received several files: *.json, file *.docx, *.xlsx and *.pdf.
What we did:
1. A personal project manager was immediately assigned to the client.
2. We determined the exact scope of work, agreed on the time and price. By the way, our timeframes were quite tight, we agreed on the translation of 36287 words within 5 days.
3. Then, we confirmed with the client the purpose of the translation, as well as the target audience, in order to best localize the application to a specific target audience.
4. Before starting the work, the project manager put together a team of relevant specialists.
5. Next, the team was trained to work on the task. The terminology base was compiled, the team was introduced to the client’s requirements. Only synchronous teamwork can guarantee the unity of terminology and high-quality translation.
6. Finally, the team moved to the main stage of work. Since the scrum methodology was chosen as the methodology of the task, the team reported, on a daily basis, to each other on the work done, without the intervention of the manager. The whole team was responsible for this project. The project manager established an uninterrupted process of submitting the finished material, so the translators sent the ready content to the manager every day at the agreed time, and then the material went to the editor.
7. Due to the coordinated work of the whole team, the translation was ready on time.
8. Testing. There are cases when the translated fragment of the text contains more words than the original fragment, as a result of this the layout may be lost. Such problems are solved in cooperation with the client: the text of the fragment can be changed to the required number of words or rewritten.
Result: An on-time translation and localization of the application containing 36287 words. At the same time, other orders were coming in, and this did not affect the task of localizing the application.
