As my app has scaled to 11 languages, the current internal translation tools in FlutterFlow have become unusable due to UI limitations and the risk of overwriting verified data. I am requesting CSV Import/Export capabilities and granular column locking to allow for professional-grade localization workflow.
Current Pain Points:
UI Scalability: With 11 languages, the table spans across two monitors. The column headers disappear upon scrolling, making it impossible to track which language is being edited.
Data Integrity: There is no safe way to add a new language (e.g., Language #12) without risking the overwrite of verified translations in Languages #1–11. The "Translate All" function is too destructive, and the "Fixed" row setting does not allow for new empty fields to be populated selectively.
Proposed Solutions:
1. CSV/JSON Import & Export (Critical)
Please add the ability to export the entire translation table to CSV/JSON and import it back in.
Why: This solves the UI scalability issues immediately. It allows developers to manage translations in Excel/Sheets, use external professional translators, or run bulk AI operations without fighting the FlutterFlow UI bugs.
2. Language-Specific Column Locking
Currently, we can only lock a "Key" (Row). We need the ability to lock a "Language" (Column).
Why: If I have verified my Spanish and French translations, I need to lock those columns so that when I generate translations for a new language (e.g., German), I do not accidentally overwrite the verified work. Currently, adding a new language requires manual entry phrase-by-phrase to ensure safety.
3. Integration of "Language Dependent Text"
Language-dependent text values (from the widget tree) should be centralized in the Settings > Languages table alongside standard app strings.
Why: My app has ~700 of these values. Currently, they must be updated manually one by one. They should be accessible for bulk translation and included in the Import/Export file.
4. LLM-Powered Translation Context (OpenAI/Gemini Integration)
Google Translate often misses context (e.g., translating "Home" as the building "Hogar" rather than the screen "Inicio").
Why: Allowing users to connect their own OpenAI API key (or offering a premium AI tier) would allow us to pass system instructions (e.g., "Translate for a mobile app interface"). This ensures contextually accurate terminology.
5. Character Count Constraints
Please add a feature to define a max character count per string, or a "Conciseness" toggle for the translator.
Why: Languages like Spanish often expand by 30-50% compared to English, breaking UI elements. We need a way to instruct the translation engine to prioritize brevity to fit within button/label constraints.