Design Systems & Component Libraries · Lesson

Internationalization (i18n)

Design and develop components that seamlessly adapt to different languages, cultures, and regional preferences.

Internationalization (i18n) is a free Design Systems & Component Libraries lesson on CoddyKit — lesson 2 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Design Systems & Component Libraries learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

Intro to Internationalization

Internationalization (i18n) is the process of designing and developing your components and applications so they can be easily adapted to different languages, regional differences, and technical requirements of a target country, region, or culture.

Think of it as preparing your product for the world! It's not just about translation, but about making sure your UI works everywhere.

Understanding Locale

A locale is a set of parameters that defines the user's language, country, and any special variant preferences that should be used to present information.

en-US: English (United States)
fr-CA: French (Canada)
es-MX: Spanish (Mexico)

These codes help your system know how to format things correctly.

Translating Text with Keys

Instead of hardcoding text directly into your components, you use translation keys. These keys are like placeholders.

For example, instead of "Hello", you might use a key like "greeting.hello". Your application then looks up the actual translated text for that key based on the user's locale.

Code: Dynamic Greetings

Here's a conceptual example of how translation keys work. The getTranslatedString function would fetch the correct text based on the locale from a translation file.

public class Greeter {
  public static String getTranslatedString(String key, String locale) {
    if (locale.equals("en-US")) {
      if (key.equals("greeting.hello")) return "Hello!";
      if (key.equals("action.welcome")) return "Welcome!";
    } else if (locale.equals("es-MX")) {
      if (key.equals("greeting.hello")) return "¡Hola!";
      if (key.equals("action.welcome")) return "¡Bienvenido!";
    }
    return "Translation missing for " + key;
  }

  public static void main(String[] args) {
    String userLocale = "es-MX"; // Imagine this comes from user settings
    System.out.println(getTranslatedString("greeting.hello", userLocale));
    userLocale = "en-US";
    System.out.println(getTranslatedString("action.welcome", userLocale));
  }
}

Adapting Dates & Times

Dates and times are presented differently around the world. For example, "03/04/2023" means March 4th in the US but April 3rd in many other countries.

Your design system components should use locale-aware formatting utilities to display dates and times correctly for the user's region.

Formatting Numbers & Money

Number formats also vary. The decimal separator can be a dot (.) or a comma (,).

US: 1,234.56
Germany: 1.234,56

Currencies need their symbol and correct placement (e.g., $100.00 vs. 100,00 €).

Handling Text Direction

Most languages read from Left-to-Right (LTR). However, languages like Arabic, Hebrew, and Farsi read from Right-to-Left (RTL).

For RTL languages, the entire layout of your components needs to be mirrored. This includes text alignment, icon placement, and the flow of elements.

Cultural Imagery

Sometimes, images, icons, or even videos need to change based on the user's culture or region.

A picture that resonates well in one country might be confusing or even offensive in another. Your design system should support managing and delivering locale-specific assets.

Design Systems for i18n

A design system is key for good i18n because it provides:

Centralized Translations: All strings managed in one place.
Adaptable Components: Components designed to handle varying text lengths and RTL layouts.
Consistent Formatting: Standardized date, time, and number formatting.

This ensures a consistent global experience.

i18n Quick Check

You're building a button component for your design system. Which of these is the BEST practice for displaying the button's text to support internationalization?

i18n Recap

We've explored Internationalization (i18n), understanding that it's more than just translation.

We learned about locales and how they define regional preferences.
We saw how to use translation keys for dynamic text.
We discussed adapting dates, numbers, currencies, and layouts (RTL).
And finally, how a design system provides a powerful foundation for building globally-ready components.

Keep these principles in mind for truly global products!

Frequently asked questions

Is the “Internationalization (i18n)” lesson free?

Yes — the full text of “Internationalization (i18n)” is free to read here on the web, and the Design Systems & Component Libraries course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Design Systems & Component Libraries course, upgrade to CoddyKit PRO.

What will I learn in “Internationalization (i18n)”?

Design and develop components that seamlessly adapt to different languages, cultures, and regional preferences. You practise Design Systems & Component Libraries with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Design Systems & Component Libraries?

No prior experience is required. Design Systems & Component Libraries on CoddyKit is structured for beginners through advanced learners; this is — lesson 2 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Internationalization (i18n)” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Design Systems & Component Libraries lesson?

Yes. Every Design Systems & Component Libraries lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

← Back to Design Systems & Component Libraries