The case for dynamic localization

Ever built an application with a User Interface in multiple languages? Then you’ve probably experienced the situation where you, as developer, instantly had to fix some translations or add a new language. Often, these requests come at the most inconvenient times. Wouldn’t it be great if we could decouple translations and content of the application from the actual release cycle?

Enter AppText.

AppText is a content management system specifically tailored towards applications. You can use it to manage translations (for labels, messages, etc.) but it also supports more complex content structures that you can define yourself (i.e. help pages).

With AppText and a little bit of custom code, you can easily add dynamic localization to your own applications. This post shows how to do this for JavaScript applications (actually, we’re using TypeScript, but all concepts apply to regular JavaScript as well).

A React notes example application

The example application for this post is a simple React Single Page Application to take notes.


Nothing fancy, but just enough for a complete example. In this post specifically, we are going to localize the labels and error messages.

A working example application can be seen live at

Go to to check out the complete source code for the example application. The readme also contains instructions how to setup AppText as backend for the example.

Translating labels and messages with i18next

The i18next library is my weapon of choice when it comes to JavaScript localization. It’s not tied to a specific framework and has plugins to cover probably all possible scenarios.

AppText comes with the Translations module that provides HTTP endpoints specifically tailored towards localization libraries. Configuring i18next to use AppText as backend for translations is super easy. We just use the i18next-http-backend plugin. This is the i18next configuration of the example application:

import i18n from 'i18next';
import { initReactI18next } from 'react-i18next';
import Backend from 'i18next-http-backend';
import { appTextApiBaseUrl, appTextAppId, currentLanguageStorageKey, appTextApiKey } from './config';

const language = localStorage.getItem(currentLanguageStorageKey) || 'en';

    lng: language,
    fallbackLng: 'en',
    returnNull: false,
    backend: {
      loadPath: `${appTextApiBaseUrl}/${appTextAppId}/translations/public/{{lng}}/{{ns}}`,
      customHeaders: {
        'X-Api-Key': appTextApiKey,
        // ...
    debug: true,
    ns: ['labels', 'messages'],
    defaultNS: 'labels'

export default i18n;

This is a straightforward configuration for i18next in a React application.

The AppText-specific part of the configuration above is in the backend property of the init() options:

backend: {
  loadPath: `${appTextApiBaseUrl}/${appTextAppId}/translations/public/{{lng}}/{{ns}}`,
  customHeaders: {
    'X-Api-Key': appTextApiKey

The loadPath property points to the AppText Translations endpoint. To access this endpoint, an ApiKey is required.  We add this key with a custom HTTP Header X-Api-Key.

You can see a few variables in the loadPath that require some explanation:

appTextApiBaseUrl The base address of the AppText installation (e.g.
appTextAppId The id of the AppText app that contains the context (e.g. ‘jsexample’)
{{lng}} The language for the translation. This is dynamically set by i18next
{{ns}} The i18next namespace for the translation. This corresponds with an AppText collection and is dynamically set by i18next

Let’s say that i18next is going to load all translations with namespace ‘labels’ and language ‘en’. The actual loadPath (which is the AppText endpoint url) then becomes:

Below you can see how the variables relate to the AppText Admin interface.

apptext-i18nextThat’s all we need to do to integrate i18next with AppText.

Displaying the translations in the components is straightforward i18next. In our example with use the useTranslation hook from the ‘react-i18next’ package. A nice example is the Notes list component:

import React from 'react';
import { useTranslation } from 'react-i18next';
import { Note } from './models';

interface ListProps {
  notes: Note[],
  onRemoveNote(note: Note): void 

const List: React.FC<ListProps> = ({ notes, onRemoveNote }) => {
  const { t } = useTranslation('labels');

  return (
    <section className="notes">
      <p>{t('There are n notes', { count: notes.length })}</p>
      {, idx) => 
        <div key={idx} className="card">
          <div className="heading-withbutton">
              <button onClick={() => onRemoveNote(note)}>&times;</button>

export default List;

The Notes component has two labels that are displayed with the i18next ‘t’ function that comes from the useTranslation hook:

      <p>{t('There are n notes', { count: notes.length })}</p>

In AppText, these translations are in the ‘labels’ collection:


Note that the keys for the translations are in natural language, but we could just use synthetic keys. Also, we’re using the i18next pluralization feature with the translation for key ‘There are n notes’.

What about complex content?

Sometimes, we want to display more complex content in our applications, for example, help or information pages.  Can we use i18next for those as well? In theory, yes, but with AppText we have more options with custom content types and the GraphQL API. That’s something we’ll cover in the next post.

Dynamic localization of JavaScript apps with AppText and i18next
Tagged on:             

Leave a Reply

Your email address will not be published. Required fields are marked *