How-to? - Page 1 - Applanga

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 https://dashboard.applanga.com/ as Base URL and https://dashboard.applanga.com/auth/okta/callback as Login redirect and add a checkbox at Authorization Code 5. Send a mail to info@applanga.com 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... »

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 'https://github.com/CocoaPods/Specs.git' platform :ios, '9.0' #source "https://github.com/CocoaPods/Old-Specs" #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... »

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": {... »

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

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

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