Localisation is not translation with renamed buttons
A product is localised when it feels as if it was built for that market. Spanish users have specific expectations around formality of address (tu vs usted), date and number formatting, legal disclosures that reference Spanish consumer law (Real Decreto Legislativo 1/2007), and communication tone that reads as natural rather than imported. Software translated word-for-word from English rarely meets these expectations.
What we localise
- UI string files (.json, .po, .strings, .resx, .xliff, YAML)
- In-app help content, tooltips and contextual guidance
- Knowledge base articles and support documentation
- App Store and Google Play listings and screenshot text
- Marketing websites and landing pages
- Email sequences and user onboarding flows
- Terms of service, privacy policies and RGPD notices
Spanish-specific considerations
Spanish text typically runs 20 to 25 percent longer than equivalent English text. UI components designed for English strings will need to accommodate this expansion without breaking layouts. We flag string length issues during translation and provide character-limited versions where hard UI constraints exist. Spanish consumer law also requires specific formulations for subscription cancellation, automatic renewal disclosures, and withdrawal rights that must be reflected in product copy.