AI-generated UI text is written to the default-language slot regardless of input language

Bug reports
1

When generating UI with the AI feature in Create, the generated text is written to the default language slot no matter which language the prompt was written in. The project’s Internationalization settings are not taken into account.

Environment
App with three configured languages. English is default, Norwegian is second.

Steps to reproduce

  1. Open an app with Internationalization configured for three languages (English default, Norwegian second).
  2. Use the AI feature in Create and write the prompt in Norwegian.
  3. Let the AI generate a UI component.
  4. Inspect the generated text in the Internationalization settings.

Expected result
The Norwegian text is stored in the Norwegian slot. Either the English slot is filled with a translation, or it is left empty and flagged as missing. Generated functions return strings based on the active language setting.

Actual result
The Norwegian text is stored in the slot reserved for English. The Norwegian slot is left empty. Generated functions contain hardcoded strings with no reference to the multilingual setup.

Impact
Every generated component has to be corrected manually: the text must be moved to the correct language, the English version written from scratch, and the functions rewritten to be language-aware. This removes most of the time saved by using the AI feature.

Suggestion
The AI already has access to the Internationalization settings, so it should be able to place terms in the correct slots and generate functions that return strings according to the active language. Appfarm uses the same AI model I use myself to produce correct translations whenever the built-in Google Translate falls short — which it does most of the time.

2

Hi lbj,

Thanks for the clear repro steps, and for the feedback in general. This is a known limitation — the AI doesn’t yet work with the Internationalization/language-slot structure when generating text, so it writes everything into one slot regardless of prompt language.

We’re hoping to get this implemented this autumn, though priorities shift a lot so I can’t promise a firm date. In the meantime, a workaround: prompt in your default language, then fill the other language slots via Google Translate/manual translation in Internationalization, and adjust generated functions for Active Language manually.

Best regards
Synne