

EdTech / Online Learning
Ongoing web, iOS, and Android interface localization across an unusually broad set of languages, integrated directly into the client's own codebase
Evolve needed to translate its web platform and native iOS and Android apps beyond their English base into a long and unusually specific list of languages - including regional variants that aren't standard offerings, such as Uzbek in both Latin and Cyrillic script, and Portuguese for both Portugal and Brazil. Each platform used its own file format (PO for web, .strings/.xcstrings/.stringsdict for iOS, .xml for Android), and every technical marker - placeholders, plural rules, formatting tags - had to stay intact so translated files could drop straight back into the existing codebase without manual rework.
Built a CLI-based workflow that reads and writes each platform's native localization file format directly, so each platform team could translate its own strings from inside its own codebase and pipeline, without spreadsheets or manual handoffs between platforms.
Delivered an unusually broad and specific language matrix - including rare regional variants like Uzbek Cyrillic and Brazilian versus European Portuguese - adding new locales quickly as new markets and clients came up, including turning around a brand-new locale within days for a time-sensitive request.
Extended the same CLI-based approach to translating marketing and transactional HTML email templates, preserving formatting and markup so only the visible text changed.
Built and maintained a shared glossary to keep interface terminology consistent across languages and platforms, including specialized domain vocabulary for the client's own use cases.
Ongoing, actively used localization coverage across web, iOS, and Android spanning more than a dozen languages, including several regional variants rarely offered off the shelf.
A new locale variant delivered within days to meet a specific, time-sensitive client deadline.
A stable, evolving integration that has stayed active for over a year as the client's platform, language list, and content formats - interface strings, then HTML templates - kept expanding.
Before Algebras: Evolve's interface strings for its web platform, iOS app, and Android app existed only in English, with no shared workflow to extend new languages across three different codebases and file formats at once.
After Algebras: A single CLI-based workflow, run from inside each platform's own codebase, keeps web, iOS, and Android interface strings - plus HTML email templates - in sync across a wide, evolving list of languages, including several rare regional variants.