This is a licensed feature which can be enabled by your BRYTER contact person. For further information, please reach out to them or
support@bryter.io.
Additional pricing may apply.
BRYTER makes it simple to localize your applications so you can deliver them to end users in multiple languages.
The process is straightforward: first add your languages, then provide translations, and finally publish and activate them for end users.
How to create and publish multi-language applications
1. Add languages to your application
- Open your application and go to Languages in the sidebar.
- Add or remove languages. (See the list of supported languages.)
- Click Save configuration.
2. Translate sidebar items
- Go to Publish in the sidebar.
- In the Sidebar section, you’ll see one column for each configured language.
- If a sidebar item is missing, click Manage sidebar items and choose which modules, data views, and pages should appear in the application sidebar.
- Add translations for each sidebar item.
- A warning icon highlights missing translations.
- Remember to click Save changes to store translations. These changes are saved but not yet applied to your Test or Live environments. This allows you to work on translations without impacting your published application.
- Once translations are ready, publish your application to Test, Live, or client environments.
3. Activate languages
- In the published application, open the three dot icon and select Localization.
- Choose the languages you want to make available for your end users.
4. Enable the language switcher (optional)
- If you tick Enable language selection, a language switcher will appear in the top-right corner of the application for your end users.
If you want to enable the language switcher for a stand-alone module, please refer to this documentation.
Good to know
- Missing sidebar translations fall back to the application’s default language.
- If a user switches to a language that a module does not support, that module will fall back to its own default language.
- Module content (e.g., text within modules) must be translated separately. See: Deliver a Module in Multiple Languages.