💬 New input component: "Multilanguage Text" Same as text-component but with multiple language variants inside the component, shown as tabs (e.g., ENG, FIN, SWE, etc) for easy switching and editing per language. 🧩 “Add Languages” Integration in Settings The selected languages here (checkboxes with defined languages) should automatically define which tabs appear in text components. Here you can also set a fall-back lang. 🪄 Magic Translate Button Add a one-click “Auto-translate all” button inside each multilanguage text field that uses OpenAI (or similar) to translate the base language into all activated languages with empty fields (so it doesn't overwrite what's already done. This would massively reduce manual work and ensure consistency across screens. ✨ Home-screen background action When "Multilanguage text" component has been used in project, then Home screen does a quick homework on which texts to show for the user afterwards, without working this decision screen-by-screen as several workarounds do. Please see attached UI example of how this could work practically in the builder interface. Why this matters: 🌐 The world is not monolingual. Supporting multilingual apps natively is not just a nice-to-have. It’s a necessity in many markets and no plugin or workaround today works seamlessly. Every attempt at solving this with custom components or visibility conditions introduces 1-2 sec delays when switching screens (when workaround is screen-based) or 4–7 sec home screen load during launch (one new plugin that I found recently from outside of official Adalo marketplace). Native multilanguage support with auto-translation would make Adalo the go-to choice for international creators and app entrepreneurs. Please consider prioritizing this. It’s a game-changer! 🙏 Building with Adalo 4 years now. Has 4 active apps in app stores that uses a total of 17 different languages.
