1. Adding the enabling technology
Integrate our Nativer SDK into your app to get dynamic resource jvnsvdcapability.
Test the scope of dynamic resource management (strings to be localized) and that your app functionality remained intact.
2. Configuring and publishing
Your app is ready for publishing without translations - dynamic resource management enables translations to be build and downloaded later on the released product.
Configure each languages how the translations are built on the Nativer service portal such as enabling/disabling translation, quality of translation and who can translate it.
Configure your analytics using our APIs to understand user behavior by language versions, and the community localization activity.
Publish your app on GooglePlay or to beta channel based on your localization strategy.
3. Translating the app
You don’t need to do anything. After your app started by the users, a new function – language setting – initiates a new type of user engagements. User can select to become translators/reviewers – invoking the automatically downloaded translator app for on device in-app translation.
4. Using the app
After your app started, a new function – language setting – initiates a new type of user engagement Users can vote for new translations, download finalized translations, reporting translation issues and use your app for language practicing as well.
As a publisher review the analytics data to understand the user behavior impact of language versions and user language needs and localization activities. Reconfigure your language setting on Nativer service portal anytime based on these learnings.
Details (Adding enabling technology and Configuring and Publishing)
Integrating the enabling technology take 15 minutes to 1,5 hours based on your IDE environment. After you build in our SDK your app will be ready for dynamic localization, so your APK can be published without build in language resources.
You will need your app’s source code and the ability to deploy a software component and build your app.
1.1 Integrate Nativer SDK into your app
using Android Studio install the “Android On-device Resource Localization” plugin from the IntelliJ repository and start the wizard. How?
using Eclipse. How?
using Gradle. How?
1.2 Test the integration and dynamic localization capability.
Test your app that all functions works as before the integration
Test that all to be translated strings are recognized by the SDK. How?
Publish your app without translations - dynamic resource management enables translations to be build and downloaded later on the released product. You can configure how the translations are built on the Nativer service portal and use the analytics API for measuring language impact.
All configuration task is done on the Nativer Service Portal – you will need the username and password generated in the previous step. Additionally for configuring analytics you need able to insert tracking code into your app.
2.1 Language setting
Based on your current localization status you can
enable/disable dynamic localization
enable/disable for users to download machine localization
setup who can improve machine localization – anybody/invited users
setup how localization approved – automated based on statistics/invited users
Set languages here
2.2 Analytics setting (optional)
Two sets of analytics available. For understanding how localization impacts your use behavior analytics API provided which you can integrate into your overall analytics.
User language needs and localization activities tracked as separate data. We suggest to track these events as separate entities.
Set analytics here
Publish your app on Google Play or on beta networks. On markets you disabled for dynamic resource localization user will see no change in your app. On markets which enabled for the service after the app started users will be engaged thru a popup window (language setting) /notification function. User engagement options will be dependent on language configuration and availability of the translations for the specific language.