Where should language localization occur: client-side or server-side?

Frontend
1

Hey everyone,

I’m working on a web app using AngularJS for the front-end and a Java API for the back-end. I’ve already set up error message localization on the server, but I’m not sure about the best approach for translating API responses.

Here’s my dilemma: should I translate the data on the server before sending it to the client, or should I send the original data and let the front-end handle the translation?

For example, if a French user requests info about a fruit, should my API return the details in French, or should I send the English version and let AngularJS translate it?

I’m curious about the pros and cons of each method. What’s the common practice in web development? Any advice would be great!

// Client-side translation example
function translateFruit(fruit) {
  const translations = {
    apple: 'pomme',
    banana: 'banane',
    orange: 'orange'
  };
  return translations[fruit] || fruit;
}

// Server-side translation example
public class FruitTranslator {
  private Map<String, String> translations;
  
  public String translate(String fruit) {
    return translations.getOrDefault(fruit, fruit);
  }
}

Thanks in advance for your input!

2

From my experience, server-side localization is often the preferred approach for several reasons. It ensures consistency across all clients, reduces the payload sent to the client, and improves initial load times. It’s also beneficial for SEO as search engines can easily index localized content.

However, it does increase server load and can be less flexible for real-time language switching. A hybrid approach could be a good compromise - serve critical content localized from the server, but allow client-side translation for dynamic or less important elements.

Consider your specific use case, the volume of translatable content, and your performance requirements. If your app needs frequent updates or supports many languages, client-side might be more manageable. But for most scenarios, I’ve found server-side localization to be more robust and efficient in the long run.

3

Hey there! client-side translation sounds intriguing. have u considered using a CDN for ur translation files? it could help with performance. also, what about SEO? server-side might be better for that. hve u thought about a hybrid approach? jst curious about ur thoughts!

4

hey silvia, i’d go with client-side translation. it’s more flexible and easier to update. plus, it reduces server load. just make sure to cache translations locally.

but watch out for performance hiccups with big translation files. also, some folks might have js disabled, so plan for that.

good luck with ur project!