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 »

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 »

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, »

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 www.applanga.com 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 »

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 »

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 »

Multilingual app development gets a facelift If you’ve ever been involved in translating or localizing a product, you know how tedious and stressful the entire process can turn out to be - from file formatting and internationalization nightmares to unexpected updates, design bugs and incorrect or missing translations. Applanga was developed specifically to address pain points traditionally encountered in the localization process that other localization tools tend not to address. As a result, the tool has been embraced by large corporations, startups, partner LSPs, and individuals who discovered that automated, independent localization process is no longer a myth, but a reality. Let’s face it – localization is too often thought of as an afterthought, a necessary evil that must »