You can edit almost every page by Creating an account and confirming your email.

Applanga

From EverybodyWiki Bios & Wiki



Applanga
Type of site
Language localisation management and software Internationalization and localization
Available inEnglish
OwnerMBaas Development GmbH
Websitewww.applanga.com
CommercialYes
RegistrationRequired
Usersover 10.000
LaunchedMay 2015; 11 years ago (2015-05)
Current statusonline

Applanga is a proprietary web-based live translation management system, also known as Globalization Management System (GMS) mainly targeted at app and game developers. Competitors include PhraseApp, OneSky, Smartling, Transifex and localize.io.[1][2] It is mainly targeted at app and game projects and allows the automation of translation workflows through SDKs for iOS, Android and Unity as well as an REST API for web and other platforms.[3]

Applanga is offered as a software as a service for commercial products and is free for projects under 1000 Monthly active users.[4]

In contrast to its competitors, the Applanga SDK allows for localization updates after the app was installed and eliminates the need to send any files around.

Description

Applanga provides a sharing and collaboration platform for localizable content, allowing translators to update software translation projects without the need of any developer involvement and rebuilds to localize apps, games and other platforms.[5]

The Applanga SDK automatically finds all translatable texts, uploads them to the web dashboard and also allows synchronizing them back at any time. In addition to that, it also can automatically take screenshots and link them to the texts on the platform to provide proper context for the translators to provide better quality translations. The web platform was written in Javascript and runs on Node.js and the MEAN STACK. SDKs are available via CocoaPods[6], Carthage, Maven as well as on GitHub.

History

Applanga started out with the idea of decoupling the app translation workflow from the normal release cycle to make life easier for developers and translators. It was originally planned and funded as an A/B testing platform called embraase that could update app content while the app was running, but pivoted its tech into what is now Applanga due to higher demand on the specific use case of live updating localizable content in apps.[7] The idea was soon met by requests from early users, and the platform was extended with many extensive team management and collaboration features, as well as localization specific features like glossaries and translation memories.[8] The company states the motto of Applanga as: "Freeing the localization process from any boundaries." [9] Applanga.com is operated by MBaas Development GmbH in Berlin, Germany.[10]

Translation Workflow Description

After the project is created in Applanga, a developer can integrate the SDK. The SDK will upload all strings from the app or game to the Applanga web platform. Managers, translators or programmers can join the project to work on the copywriting and translations together. Translated content is synchronized on every start of the app.

Supported document formats

Applanga enables a complete fileless workflow, but it also supports common file types like Android Strings, Apple Localizable Strings, XLIFF files, XML files, JSON, and Excel.

Features

  • Fileless localization workflow with automatic up and download of localizable content
  • SDK for iOS[11], Android[12] and Unity[13]
  • REST API for integration with other platforms/services[14]
  • Support for language file formats
  • Automated smart screenshots for better context[15]
  • Team Management[16]
  • Sharing language files with translators who can download, translate and update software translations online and offline
  • Glossary & Translation Memory for duplicate source content[17]
  • Commenting and translation status system for translators
  • Professional translation services and ordering

Notable users

References

External links


This article "Applanga" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:Applanga. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.