# Context

We often emphasize the importance of providing context for translators. The more context you provide, the better translation quality you can get. This is especially important when it comes to web or mobile applications. Since texts for app translation are typically short, context would help translators decide which translation variant should be used. With Crowdin, you can provide translation context in multiple ways. It can either be a textual context for every key or an in-context preview to let translators browse the web app while translating. A manager in a Crowdin project can add screenshots, so translators can see exactly how the key would be used in the app. Let’s stop on the screenshots, they are great but might be hard to add for every key and maintain them relevant as your project evolves. One of our customers – Bounce, recently implemented a great solution for managing project screenshots. The amount of screenshots they manage is huge! Bounce project has 8000 screenshots in Crowdin, covering a big part of their product – a mobile app for luggage storage and pickup and their email templates. These screenshots are being updated as the product evolves. No manual work, the whole process is automated. How can that be possible? Let’s figure it out.

The key idea behind developing Crowdin Mobile SDK was to help you make the apps you build accessible to global customers faster, keeping your data secure, and ensuring the high quality of translation. Hence, Over-the-Air Content Delivery allows you to update the translated strings of the iOS and Android apps instantly. Without submitting a new app version on the App Store or Google Play each time new translations arrive. Along with CDN, Crowdin Mobile SDK allows you to set up two additional features. Both Screenshots and Real-Time Preview are not aimed at your end-users but will help to give translators functional and visual context. Learn how you can integrate SDK extras in your app localization workflow and get better translations.

If you deal with localization and expect accurate translations, remember – context is the king. The more context you give your contributors, the better translations you get. It seems like a clear and simple idea, yet often translators are left to work out of the context. As a consequence, there are lots of back-and-forth interactions and missed deadlines you could avoid. To stay agile during localization, invest some time and provide context before the translation starts. This will pay off in the long run. This article includes a brief overview of all the ways to provide context in Crowdin. So that you can always be sure your translators have an excellent work environment.

The more people are translating your project, the less time it takes to receive results, no one can doubt that. But there’s no guarantee that translations made by several people will be consistent in tone of voice, wording, and terminology usage. A glossary is one of the resources that should be added to help your translators understand the key terminology and how it should be translated. In this article, we’ll show you how a termbase can improve your localization process, then explain how to build and translate a glossary. Storing your glossary in your localization platform is a great way to enhance collaboration between everyone involved in the project.

Did you know that simply great translations might not always be the same as relevant to your app translations? Accurate translations depend on many factors such as translation context, the translation team you choose, quality of the source strings, and many other things. Companies usually concentrate on the translation team and often overlook the importance of providing translation context. Which tends to result in poor quality translations or the ones that aren’t relevant to your app.