Enhancing User Experience through Localization in VBCS
Localization helps a Visual Builder application serve users in different languages and regions without duplicating the application. The following strategy keeps interface text in translation bundles, selects a locale at runtime, and maintains consistent keys across every supported language.
Configuration Example
"localization": {
"locale": "{{ window.localStorage.getItem('vbcs.languageSwitcherApplication.locale') || 'en' }}"
}Steps for Applying Localization
Mark Labels for Localization
Select each component label in the UI Editor and use the Label Hint localization option. Only properly marked labels will be included in the translation JSON.
Create a Translation Key
Assign a clear, unique key to every translatable value. Consistent keys make translations easier to manage across the application.
Verify Translation Files
Open the application strings file and confirm that each key exists and maps to the intended source value.
Deploy Language Bundles
Upload translated language bundles (such as Arabic, Spanish, French) and verify runtime locale switching.
Localization Best Practices
Conclusion
A well-structured localization workflow makes VBCS applications easier to use across languages and regions. By centralizing strings, preserving translation keys, and validating each bundle, teams can deliver consistent multilingual experiences without maintaining separate applications.
