Setup for Cordova translations is simple

Cordova is a container for running a web application like it was a native app. So the web app written in HTML, JS and CSS can access the native device functionality like camera or GPS, which otherwise would not be possible. In Cordova setup, you need to add platforms for which you intend to publish your app. As well as, you need to install appropriate Cordova plugins to enable referring to the device resources from your web app. The technology used for translating the app itself is up to you, however there are "system" strings or push notification messages that are not accessible from your web app level. For translating those you need a Cordova Localisation String plugin. The typical... »

How to use a custom SSO Provider (Okta SSO)

As an Addon to the Applanga Enterprise tier you have the option to connect with custom SSO (Single Sign On) providers. Please get in touch for pricing details. The following is an example if you want to use Okta SSO. Applanga Okta SSO Integration 1. Click on Applications in your okta admin console. 2. Click on Add Application. 3. Select Web and then Next 4. Use as Base URL and as Login redirect and add a checkbox at Authorization Code 5. Send a mail to with the topic custom sso wich contains your Client ID, Client secret, Okta domain and a list of domains that should be enabled for your okta configuration. Alternatively and additionally you can... »

Localize libraries and sub projects with CocoaPods

If you wish to use the Applanga iOS framework in an Xcode subproject (dynamic or static lib), then you need to tell your Podfile about those projects. source '' platform :ios, '9.0' #source "" #link_with 'MyTestApp' def myPods use_frameworks! pod 'Applanga' end workspace 'MyTestApp.xcworkspace' target 'MyTestApp' do myPods end target 'MyStaticSubProject' do myPods project 'MyStaticSubProject/MyStaticSubProject' end target 'MyDynamicSubProject' do myPods project 'MyStaticSubProject/MyStaticSubProject' end The important part is to make sure you specify in the Podfile exactly where your target sub project is. That way it will install those pods for the sub project too. If you wish to localise a .strings file within a dynamic library/sub project, then all you need to do is add the following field to your... »

Localising an iOS watch app extension with the Applanga CLI

Keeping your iOS watch app extension Localised with the Applanga CLI is a quick and painless experience. Once you have your base app localisation setup to use string files, add the WatchTarget as a target for those files, that way you will be able to access the strings via their keys in your watch app. If you've read the Applanga CLI Documentation you know that in order to localize files with it you need to specify them in the configuration file (.applanga.json) and for your Localizable.strings to be included in the configuration you're config should look something like this: { "app": { "access_token": "YOUR_ACCESS_TOKEN", "base_language": "en", "pull": { "target": [ { "file_format": "ios_strings", "path": "./<language>.lproj/Localizable.strings" } ] }, "push": {... »

Localization Command Line Interface

Applanga provides native localization SDKs for iOS, Android, React Native and Unity as well as a Rest API to retrieve strings dynamically in other platforms but in some cases you want or need to keep strings in files with different localization file formats. Reasons for not using an SDK could be either you want to localize push notifications or Info.plist strings on iOS or you have a web project for Angularjs, Nodejs, Go, JSON or another format that simply needs a text file localized. That's where the Applanga Command Line Interface (CLI) fits in and helps to automate such processes by allowing up and download of files via the command line/terminal. The CLI comes as a single executable that can... »

InfoPlist.strings and iOS Push Notification Localization Automation

One of the key features that sets Applanga apart from other localization platforms are its SDKs which allow synchronizing strings from apps without the need to send files around and even without Appstore updates. But there are a few strings that the Applanga SDK cannot change at runtime because they are used by iOS directly without the running app e.g. strings for localizing push notifications and the several usage descriptions as well as the App Name defined in your Info.plist file. To automate the localization of these strings you should use the Applanga Command Line Interface (CLI). With the CLI you can up- and download .string files for your app from the command line and you can integrate that into... »

Manual & Automatic Backups

A localization project can easily become pretty complex undergoing constant changes in translation methods, workflows, and team composition. With that comes all kind of potential for error. New team members are not familiar with tools yet and accidentally overwrite translations, complete languages are deleted in the heat of the moment, miscommunication leads to somebody resetting nearly finished translation workflows or some technical error anywhere in the process leads to the wrong translations in the wrong place - we have seen it all. So far, we were always able to help our people to restore their translations but we felt it was time to hand these tools to the user base for an even more convenient experience. With our last release,... »

Game Localization: Top 5 Reasons to Localize Games

📈 Increase Your Downloads Obviously for you as a game developer it is important that as many people as possible play your game and you can only achieve that by increasing your download numbers. Games that are localized have by far a higher chance of being downloaded. If you take China for example almost 100% of the top 100 apps are localized and its very similar in Korea and Japan as well. So the overall ROI of translating a game is very high in the very huge asian game markets because of the preference of their native languages but it also shouldn't be neglected in Europe. Game sales are very high in Germany, France or Spain and even though English... »

What's Cookin?

Over the course of the last ~12 months, we've been very busy adding a lot of features on or localization platform but you probably haven't heard about it without official announcements along the way. So, I'll try to change that in this post and give a brief overview of all the latest changes. The Website To make the overall Applanga experience much smoother and to have the option for faster updates to the frontend, we've split the applanga web presence into 2 subdomains. At the front, we have which contains all marketing and explanatory content of Applanga including the documentation and this blog all pages should load a lot faster and searching for specific features should be easier. Also... »

Feature Update Glossary and Translation Memory

How to ensure consistency and stop repetitive translation efforts in your localization process We at Applanga have one mission - we want to help you optimize your localization processes. And we can’t do that without continuously optimizing our own solution. Our latest two feature updates revolve around the topic of ensuring consistency and not doing the same work over and over again. We have implemented a glossary as well as a translation memory, and would like to show you the “what, why and how” of each solution - for an even better localization workflow with Applanga. Glossary What A glossary is simply a list of terms specific to a company, product or project. It is often referred to as lexicon,... »

How to Stay Productive and Deliver Quality Translations

We know that budget constraints put real pressure on localization teams, demanding them to be both highly productive and yet still deliver top quality content to the end users. To make the best out of your resources when localizing your mobile app, follow the six steps below. 1. Eliminate Inconsistencies One of the biggest time-killers in the mobile app localization process is getting strings from the code to the translators and reviewers, then back into the code for testing and QA, possibly back to the translator and finally into the app code for the next deployment. Not only does it require numerous emails and file uploads to complete one cycle of this process, it is also very easy for mistakes... »

Why Localization is Key in FinTech

FinTech – a global trend on the rise After The Global Financial Crisis in 2008, Fin Tech companies have sprung up from all over the globe and since then formed one of the most rapidly growing industries of recent times. Global FinTech investments tripled since 2008, from $928 million to $2.97 billion and are expected to reach up to $8 billion by 2018 (Gelis, P. and Woods, T. 2014). It looks like nothing can stop FinTech companies from pushing the envelope on how financial services work, generating ever-new innovations and enabling users to handle their finances in new ways. Any trend as disruptive and fast growing as this is worth taking a closer look at. New frontiers are no longer... »

How to Simplify Mobile App Localization in 4 Easy Steps

If you are reading this, chances are that you know how tricky mobile app localization can be from first hand experience. Though it is true that many traps wait along the way – from bad translation quality over time-consuming back and forth between engineers and the localization team to being out of sync with release cycles – localization can actually be pretty darn easy. We’ve been working with localization teams all over the world for many years now and figured out the biggest hurdles, and how to jump them. 1. Stop copying and pasting strings Manually getting strings from the code to excel files that you can then send around to your translators is problematic for a number of reasons.... »

A Revolution in Mobile App Localization and Linguistic QA

It’s the crux of agile localization: how to achieve high translation quality, minimal project management and fast turnaround times while keeping up with the continuous development and release cycles of an app. So far, localization professionals confronted with this challenge had to make a trade-off: either slowing down all other processes for the sake of higher translation quality or live with the fact that there might be wrong translations in the next release because there wasn’t any time for linguistic QA. And while this tradeoff can theoretically be circumvented by throwing more manpower on it, more often than not, the localization budget limits that from being a feasible option. After analyzing a variety of mobile app localization workflows and extensively... »

Why is context important when localizing mobile apps?

You might think that most translators are given context for the subject that they are translating. However, more often than not, translation occurs separately with the product out-of-view, so translators are given very little if any context at all to help them understand exactly what they are translating. What do you mean by “context?” Translating in context involves being given additional information during the translation process to see or understand how a translation will be used in the final product. A great example is character limits. If you’ve ever used a product that was originally created for another language, you have probably run into cut off sentences or texts that don’t fit the parameters of the button or page they’re... »

Page 1 of 2