i18n - Internationalisation
Transforming Pronto Xi for International Markets. The Pronto Lexicon project aims to enhance Pronto Xi for international markets by enhancing its language capabilities. At present, Pronto Xi does not offer robust language support for internationalisation. As businesses continue to expand globally, the need for software that meets diverse linguistic requirements is increasing. The Pronto Lexicon project aims to address this by incorporating new language support and translation features into Pronto Xi.
Pronto Xi ERP | Global SaaS Platform | Scalable UX & Localisation System
One - Click Automated Translation process (Sys. Admin)
Scope of Pronto Xi i18n
One - Click Automated Translation process (Sys. Admin)
Overview
Led the redesign of internationalisation (i18n) experience and framework in Pronto Xi to support multi-language, multi-region users while maintaining usability, consistency, and scalability.
The goal was to transform i18n from a fragmented, inconsistent implementation into a system-driven, scalable UX approach across the product.
Problem
The product faced major challenges when expanding globally:
-
Hard-coded text across the system
-
Inconsistent translations and terminology
-
UI breakage due to text expansion (e.g. German, French)
-
Poor readability and usability in non-English languages
-
No standard process for managing translations
This casued:
-
Poor user experience for global users
-
Increased support issues
-
High maintenance effort for teams
Users
-
Global customers across 5+ regions
-
Non-English speaking users
-
Internal teams managing translations
My Role
Lead UX Designer (Product role)
Owned i18n UX initiative across the platform:
-
Discovery → Problem definition → UX framework → Validation → Rollout
Collaborated with:
-
Product & Engineering
-
Translation teams
-
Global stakeholders
DESIGNS
UX PROCESS (SYSTEMS + SCALABILITY)
1. Discover
Methods:
-
UI audit to identify hard-coded text and inconsistencies
-
Analysis of translation issues across modules
-
Feedback from global users and stakeholders
-
Review of localisation workflows
Key Insights:
-
i18n was treated as a technical afterthought, not a UX problem
-
Translations failed due to lack of context and structure
-
UI was not designed for language flexibility
Insight:
Internationalisation is a system design problem, not just translation
2. Define
Reframed the problem:
No -> “Fix translations”
Yes -> “Design a scalable i18n system that supports global usability and consistency”
Key Goals:
-
Ensure UI works across languages
-
Improve translation quality and consistency
-
Enable scalable localisation
-
Maintain usability across regions
3. Design (i18n UX System)
1. Standardised Content Structure
-
Eliminated hard-coded text (Dictionary Level)
-
Introduced structured, reusable content keys
Enabled scalable translation management
2. UI for Language Flexibility
-
Designed layouts to handle text expansion and contraction
-
Ensured responsive behaviour across languages
Prevented UI breakage
3. Consistent Terminology System
-
Standardised key terms across the platform
-
Ensured consistent language across modules
4. UX Guidelines for i18n
-
Defined best practices for:
-
Text length
-
Labels
-
Error messages
-
Date/time formats
-
API & Integration Layer (Scalable i18n)
To support a scalable and efficient internationalisation system, I worked closely with Engineering to integrate translation APIs and automation workflows into the product.
API Integration Approach
-
Leveraged Google Cloud Translation API for dynamic translation support
-
Designed workflows for automated translation generation and fallback handling
-
Enabled seamless integration between UI content and translation services
4. Prototype & Validate
Methods:
-
Multi-language UI testing
-
Layout testing for text expansion
-
Feedback from global users
Focus:
-
Readability
-
Layout stability
-
Consistency
DESIGN APPROACH
Systems Thinking
Designed i18n as a cross-product system, not a feature
Scalability First
Ensured solutions worked across multiple languages and regions
Product Thinking
Balanced user experience, business expansion, and technical constraints
AI-Forward Thinking
Explored intelligent localisation and automation
KEY LEARNING
“Internationalisation is not about translating words—it’s about designing systems that work across cultures, languages, and contexts.
By treating i18n as a UX and system design problem, we enabled true global scalability.”
Translating Platforms Study - Existing Pronto Xi Translate
Integration with Google Cloud Translate API
One - Click Automated Translation process (Sys. Admin)
Drove internationalisation UX enhancements in Pronto Xi ERP by auditing and standardising UI content across modules. Identified translation failures and hard-coded text, and introduced structured approaches to improve consistency, scalability, and localisation readiness—enabling a more seamless global user experience.