Languages can be tough to accommodate when one is not working with a custom-built App, but there are some options that help to cater to a multi-language client base. There are just a couple of terms one needs to know as a start:
- Hard-coded: This refers to text that one can't control in Design, like home screen button text (Call Us, Directions, Tell Friend), pop-up prompts (Enable Push Notifications), and more. Anything users see in their App that they didn't write themselves is typically hard-coded. That means it's pulled from the general system-wide settings and applies to all Apps on the platform.
- Translation string: These are specific translatable words or phrases.
The hard-coded text should automatically translate into device's default language. The text one manually input (tab titles, anything added in Design) will not auto-translate. It will appear as-is for all users. If one wants their App to serve more than one language, it's best to duplicate one's content for each language. (For example, in an Info feature the user would translate their item description into another language below their English description.) The best option is to create another version of the App for each additional language. This provides the best user experience.
Note: Default translations will apply to one's App if one is a free trial user or Single App Client.
Resellers can add their own custom translations for client panel and Apps. This allows Resellers to override the system's default hard-coded text for each available translation string. (For example, if the Call Us button needs to be changed just to say Call, the Reseller can translate it to that, and this change applies to all Apps in the respective Reseller's account.) It's important that one selects the correct language from the drop-down menu on the top right before beginning their translations. The default selection is English.
The Multi-Language add-on is usually used for more than 2 languages and it is on a per app basis!. The multi language add-on is for translating content (ie what you put in your feature) and not system staff (that are auto-translated in the most popular languages, at least)