🌍 Native multilingual support without duplicating columns

[Darren_Murphy]

@Alexis-Driing

Today, when we want to create an app in multiple languages, we have to duplicate every text field for each language (FR, EN, ES, etc.)

No, that’s not necessary at all.

@Alexis-Driing

• A single text field containing all translations in a structured way (like JSON or key-value pairs),
• And automatically display the right language version based on the user’s settings?

That’s exactly what I usually do.

Best way to create an app with multiple languages

Not exactly. I’ve been using variations of this approach for about 3 years now, and the approach has evolved and been refined with each new App that I’ve implemented it in. The current approach works as follows: I have a separate “Strings” table. This table has one row for each text snippet that is used anywhere in the App. I have a JSON column that contains the translations for each supported language. It looks something like this: { "translations": { "zh": "输入总工作时间", "ms": "Masu…

There is also https://www.weglot.com/, which I know others have used successfully with Glide Apps.