Applanga SDK for iOS Localization

Version: 2.0.82



CocoaPods [?]

  1. Refer to CocoaPod’s Getting Started Guide for detailed instructions about CocoaPods.

  2. After you have created your Podfile, insert this line of code: pod 'Applanga'

  3. Once you have done so, re-run pod install from the command line.

Carthage [?]

  1. If you are new to Carthage, please refer to their documentation first.

  2. Add the following line to your Cartfile github "applanga/sdk-ios" ~> 2.0.

  3. Run carthage update from the command line and link the Applanga.framework to your project as it is described in the carthage documentation: Getting started for iOS.

Manual (zero-code)

  1. If you want to translate your iOS app download the latest release of the Applanga iOS SDK from Github. Unzip it, then drag and drop Applanga.framework into into the Embedded Binaries section of your target and check the "Copy items into destination group’s folder (if needed)" option.

  2. Under the Build Settings tab, you need to change Basic to All and search for Other Linker Flags. Double click on the white space to the right of Other Linker Flags and a popup will open. Click the plus (+), and add -ObjC, -lsqlite3, -lz.

  3. To be able to properly upload your app to iTunesConnect you need to work around an App Store submission bug triggered by universal binaries. To do that add a new Run Script Phase in your target’s Build Phases. IMPORTANT: Make sure this Run Script Phase is below the Embed Frameworks build phase. You can drag and drop build phases to rearrange them. Paste the following line in this Run Script Phase's script text field:

     bash "$BUILT_PRODUCTS_DIR/$FRAMEWORKS_FOLDER_PATH/Applanga.framework/"


  1. To start iOS Localization with Applanga download the Applanga Settings File for your app from the App Overview in the dashboard by clicking the [Prepare Release] button and then clicking [Get Settings File].

  2. Add the Applanga Settings File to your apps resources. It will be automatically loaded.

  3. Now, if you start your app you should see a log message that confirms that Applanga was initialized or a warning in case of a missing configuration.

  4. To make sure your settings file is always up to date for every build see the doc section about Automatic Applanga Settings File update in the Optional settings

NOTE: To have native iOS dialogs properly translated and to show your supported languages on the Appstore you need to have atleast one .strings file bundled with your app for every language. (The file can be empty)



NOTE: If you do not specifiy a default value the string will not be created on the Applanga dashboard.


Besides the Basic usage Applanga offers support for named arguments in your strings, pluralisation, partial updates to save space and bandwith as well as translation of html and javascript content in UIWebView instances.

  1. Code Localization

    1.1 Strings

     // get translated string for the current device locale
     [Applanga localizedStringForKey:@"APPLANGA_ID" withDefaultValue:@"default value"];
     Applanga.localizedString(forKey: "APPLANGA_ID", withDefaultValue: "default value")

    1.2 Named Arguments

     // if you pass a string:string dictionary you can get translated string
     // with named arguments. %{someArg} %{anotherArg} etc.
     NSDictionary* args = @{@"someArg": @"awesome",@"anotherArg": @"crazy"};
     [Applanga localizedStringForKey:@"APPLANGA_ID" withDefaultValue:@"default value" andArguments:args]
     var args: [String: String] = ["someArg": "awesome", "anotherArg": "crazy"];
     Applanga.localizedString(forKey: "APPLANGA_ID", withDefaultValue: "default", andArguments: args)


    APPLANGA_ID = "This value of the argument called someArg is %{someArg} and the value of anotherArg is %{anotherArg}. You can reuse arguments multiple times in your text wich is %{someArg}, %{anotherArg} and %{someArg}."

    gets converted to:

    "This value of the argument called someArg is awesome and the value of anotherArg is crazy. You can reuse arguments multiple times in your text wich is awesome, crazy and awesome."

    1.3 Pluralisation

     // get translated string in given pluralisation rule (one)
     [Applanga localizedStringForKey:@"APPLANGA_ID" withDefaultValue:@"default value" andArguments:nil andPluralRule:ALPluralRuleOne]
     Applanga.localizedString(forKey: "no default", withDefaultValue: "default", andArguments: nil, andPluralRule:

    Available pluralisation rules:


    you can also specify a quantity and Applanga will pick the best pluralisation rule based on:

     // get a string in the given quantity
     [Applanga localizedStringForKey:@"APPLANGA_ID" withDefaultValue:@"default value" andArguments:nil andPluralRule:ALPluralRuleForQuantity(quantity)]
     // or get a formatted string with the given quantity
     [NSString localizedStringWithFormat:[Applanga localizedStringForKey:@"APPLANGA_ID" withDefaultValue:@"default value" andArguments:nil andPluralRule:ALPluralRuleForQuantity(quantity)], quantity]
     // get a string in the given quantity
     Applanga.localizedString(forKey: "APPLANGA_ID", withDefaultValue: "default value", andArguments: nil, andPluralRule: ALPluralRuleForQuantity(quantity))
     //or get a formatted string with the given quantity
     NSString.localizedStringWithFormat(NSString(string:(Applanga.localizedString(forKey: "APPLANGA_ID", withDefaultValue: "default", andArguments: nil, andPluralRule: ALPluralRuleForQuantity(quantity)))), quantity)

    In the dashboard you create a puralized ID by appending the Pluralisation rule to your ID in the following format: [zero], [one],[two],[few],[many], [other].

    So the zero pluralized ID for "APPLANGA_ID" is "APPLANGA_ID[zero]"

  2. Update Content

    To trigger an update call:

     [Applanga updateWithCompletionHandler:^(BOOL success) {
         //called if update is complete
     Applanga.update { (success: Bool) in
         //called if update is complete

    This will request the baselanguage, the development language and the long and short versions of the device's current language. If you are using groups, be aware that this will only update the main group.

    To trigger an update for a specific set of groups and languages call:

     NSArray* groups = @[@"GroupA", @"GroupB"];
     NSArray* languages = @[@"en", @"de", @"fr"];
     [Applanga updateGroups:groups andLanguages:languages withCompletionHandler:^(BOOL success) {
         //called if update is complete
     var groups: [String] = ["GroupA", "GroupB"]
     var languages: [String] = ["en", "de", "fr"]
     Applanga.updateGroups(groups, andLanguages: languages, withCompletionHandler:  {(success: Bool) in
         //called if update is complete
  3. Change Language

    You can change your app's language at runtime using the following call:

     BOOL success = [Applanga setLanguage: language];
     var success: Bool = Applanga.setLanguage(language)

    language must be the iso string of a language that has been added in the dashboard. The return value will be YES if the language could be set, or if it already was the current language, otherwise it will be NO. The set language will be saved, to reset to the device language call:


    After a successful call you need to reinitialize your UI for the changes to take effect, for example you might recreate the root Storyboard controller and present it.

    The language parameter is expected in the format [language]-[region] or [language]_[region] with region being optional. Examples: "fr_CA", "en-us", "de".

    If you have problems switching to a specific language you can update your settings file or specifically request that language within an update content call (see 2. Update Content). You can also specify the language as a default language to have it requested on each update call (see Optional settings).

     + (void) changeAppLanguage:(NSString *)language {
             [Applanga updateGroups:nil andLanguages:@[language] withCompletionHandler:^( BOOL updateSuccess ){
                     BOOL languageChangedSuccess = [Applanga setLanguage:language];
                     if(languageChangedSuccess) {
                             //recreate ui
  4. WebViews

    Applanga can also translate content in your WebViews if it is enabled.

    Add ApplangaTranslateWebViews set to YES to your Info.plist to enable translation support for all WebViews.

    To initalize Applanga for your webcontent you need to initialize Applanga from JavaScript:

     <script type="text/javascript">
         window.initApplanga = function() {
             if(typeof window.ApplangaNative !== 'undefined') { window.ApplangaNative.loadScript();
               } else { setTimeout(window.initApplanga, 180); } 
           }; window.initApplanga();

    4.1 Strings

    The inner text and html of tags wich have a applanga-text="APPLANGA_ID" attribute will be replaced with the translated value of APPLANGA_ID

     <div applanga-text="APPLANGA_ID">
             ***This will be replaced with the value of APPLANGA_ID***

    Alternatively you can call Applanga.getString('APPLANGA_ID') directly.

    4.2 Arguments

    You can pass arguments with the applanga-args attribute. By default the arguments are parsed as a comma seperated list wich then will replace fields as %{arrayIndex}.

     <div applanga-text="APPLANGA_ID" applanga-args="arg1,arg2,etc">
         ***This will be replaced with the value of APPLANGA_ID***
         ***and formatted with arguments***

    Direct call :

     Applanga.getString('APPLANGA_ID', 'arg1,arg2,etc')

    To define a different separator instead of , e.g. if your arguments contain commas use applanga-args-separator.

     <div applanga-text="APPLANGA_ID" 
             ***This will be replaced with the value of APPLANGA_ID***
             ***and formatted with arguments***

    Direct call :

     Applanga.getString('APPLANGA_ID', 'arg1,arg2,etc', ';')

    One Dimensional JSON Objects can also be used as Named Arguments if you add applanga-args-separator="json"

     <div applanga-text="APPLANGA_ID" 
          applanga-args="{'arg1':'value1', 'arg2':'value2', 'arg3':'etc'}"
             ***This will be replaced with the value of APPLANGA_ID***
             ***and formatted with json arguments***

    Direct call :

      Applanga.getString('APPLANGA_ID', "{'arg1':'value1', 'arg2':'value2', 'arg3':'etc'}", 'json')

    4.3 Pluralisation

    To pluralize a html tag you can pass the applanga-plural-rule attribute with the value zero, one, two, few, many and other.

     <div applanga-text="APPLANGA_ID" applanga-plural-rule="one">
         ***This will be replaced with the pluralized value of APPLANGA_ID***

    Direct call :

     Applanga.getPluralString('APPLANGA_ID', 'one')

    or with arguments :

     Applanga.getPluralString('APPLANGA_ID', 'one', 'arg1;arg2;etc', ';')

    You can also pluralize by quantity via applanga-plural-quantity

     <div applanga-text="APPLANGA_ID" applanga-plural-quantity=42>
         ***This will be replaced with the pluralized value of APPLANGA_ID***

    Direct call : Applanga.getQuantityString('APPLANGA_ID', 42) or with arguments : applanga.getQuantityString('APPLANGA_ID', 42, 'arg1;arg2;etc', ';')

    4.4 Update Content

    To trigger a content update from a WebView use javascript:

     Applanga.updateGroups("GroupA, GroupB", "de, en, fr", function(success){
         //called if update is complete
  5. Automatic Screenshot Upload

    To give translators some context for translating strings, the Applanga SDK offers the functionality to upload screenshots of your app, while collecting meta data such as the currrent language, resolution and the Applanga translated strings that are visible, including their positions. Each screenshot will be assigned to a tag. A tag may have multiple screenshots with differing core meta data: language, app version, device, platform, OS and resolution. You can read more here : Manage Tags and here: Uploading screenshots.

    5.1 Make screenshots manually

    To manually make a screenshot you first have to set your app into draft mode.

    With your app in draft mode, all you have to do is to make a two finger swipe downwards. This will show the screenshot menu and load a list of tags.

    You can now choose a tag and press capture screenshot to capture and upload a screenshot including all meta data for the currently visible screen and assign it to the selected tag. Tags have to be created in the dashboard before they are available in the screenshot menu.

    5.2 Display screenshot menu programmatically

    You also have the option to open the screenshot menu programmatically, this also requires the app to be in draft mode:

     [Applanga setScreenShotMenuVisible:YES]

    5.3 Make screenshots programmatically

    To create a screenshot programmatically you call the following function:

     NSString* tag = @"MainMenu";
     NSArray* applangaIDs = [NSArrayarrayWithObjects:@"String1",@"String2",@"String3",nil];
     [Applanga captureScreenshotWithTag:tag andIDs:applangaIDs];
     var tag:String = "MainMenu"
     var applangaIDs:[String] = ["String1", "String2", "String3"]
     Applanga.captureScreenshot(withTag: tag, andIDs: applangaIDs)

    The Applanga SDK tries to find all IDs on the screen but you can also pass additional IDs in the applangaIDs parameter.

    5.4 Automated during UITests

    To capture screenshots from UITests running in xcode you first have to add a specific launch argument in your test classes setup function:

     - (void)setUp {
             [super setUp];
             XCUIApplication *app =[[XCUIApplication alloc] init];
             app.launchArguments = @[@"ApplangaUITestScreenshotEnabled"];
             [app launch];
     override func setUp() {
         let app = XCUIApplication();

    Now you can capture screenshots as shown in the following example:

     - (void)testExample2 {
         XCUIApplication *app = [app init];
         //open screenshot menu by tapping invisible Applanga button
         [app.buttons[@"Applanga.ToggleScreenShotMenu"] tap];
         //toggle tag selection
         [app.buttons[@"Applanga.SelectTag"] tap];
         //select tag named "MainMenu"
         [app.tables.staticTexts[@"MainMenu"] tap];
         //capture screenshot
         [app.buttons[@"Applanga.CaptureScreen"] tap];
         //screenshot upload takes a while so we need to wait until the screenshot menu is visible again until we can proceed
         NSPredicate *waitPredicate = [NSPredicate predicateWithFormat:@"exists == 1"];
         [self expectationForPredicate:waitPredicate evaluatedWithObject:app.buttons[@"Applanga.SelectTag"] handler:nil];
         [self waitForExpectationsWithTimeout:30 handler:nil];
     func testExample() {
         let app = XCUIApplication();
         //open screenshot menu by tapping invisible Applanga button
         //screenshot upload takes a while so we need to wait until the screenshot menu is visible again until we can proceed
         let predicate = NSPredicate(format: "exists == 1")
         let query = XCUIApplication().buttons["Applanga.SelectTag"];
         expectation(for: predicate, evaluatedWith: query, handler: nil)
         waitForExpectations(timeout: 3, handler: nil)

Optional settings

You can specify a set of default groups and languages in your plist, which will be updated on every Applanga.update() or Applanga.updateGroups() call. These groups and languages will be added to any that are specified in the call itself, they will always be requested. The Parameter value must be a string, with a list of groups or languages separated by commata.

  1. Specify default groups

  2. Specify default languages

  3. Disable upload of storyboard strings You have the option to disable the collection of storyboard strings, by setting this value to false. This will not prevent the upload of localized .strings files that you may have created for your storyboard, but will stop the default upload of the cryptic string ids that are created for text ui elements in the storyboard.

  1. Automatic Applanga Settings File update

    In case your app's user has no internet connection, new translation updates can't be fetched, so the Applanga SDK falls back to the last locally cached version. If the app was started for the first time, there are no strings locally cached yet so Applanga SDK falls back to the Applanga Settings File which contains all strings from the moment it was generated, downloaded and integrated into your app before release.

    The Applanga SDK comes with a python (2.7) script called which makes sure your app has always the latest settings file version. The script searches recursively for *.applanga files in your project and checks if a newer version is available. If so it replaces the old file with the newer Applanga Settings File from the Applanga backend.

    In XCode you go to Build Phases and New Run Script Phase and add the following line (if you are using CocoaPods):

     python "$SOURCE_ROOT/Pods/Applanga/Applanga.framework/" "$SOURCE_ROOT/$TARGET_NAME"

    or (if you are using Carthage or integrated the Applanga SDK manually):


    -- Optionally you can also run the update script manually from the command line. Navigate to the Applanga.framework directory, where is located and run: