Firebase Solution to Translation of Dynamic Content...

Step 1. Upgrade to FF Pro, this enables you to translate all of your static text within the app.

Step 2 Go to FF Settings and select the translation option, select all the locales you want and hit the Translate button.

Step 3. Go to your Firebase project and enable the \"Translate Text In Firestore\" Extension, (You need a minimum Blaze account for this as its billable).

Step 4. When configuring the extension ensure the comma separated list of locales you want, match what you selected in FF Translations Settings

Step 5. The extension default behavior is to create a single collection called \"translations\" each document will have 2 fields -\"input\" and \"translated\". The input field is where you store your text to be translated, the translated field is automatically generated and populated (after a short delay) with a map of items labelled as the locales you selected when configuring the extension. It translates the input text into all the locales at the same time.

Step 6. Back in FF create a new table called the same as you configured in the extension, in this case \"translations\"

Step 7. Add a field to the table called \"input\" Data Type \"string\", the same name as when you configured the extension (default field name).

Step 8. Go to Data Types menu accessed by the icon underneath the Firestore icon on the very far left of your Development Environment, and create a new data type called \"translated\".

Step 9. Create the fields for this data type that match the locales you previously selected, All fields should be of type \"string\"

You will end up with a list of fields that match your locales... Field Name: en, Data Type: String, Field Name: es, Data Type: String, etc.

Step 10. Go back to the translations table configuration in FF and below the \"input\" field you created a moment ago, add a new field named \"translated\".

Step 11. When selecting \"Data Type\" select \"Data Type\" (I know its confusing) near the bottom of the list of available options (currently just above Enum but this may change as the FF software gets updated.).

Step 12. You are now given an extra option to complete which is the \"Data\" field... select \"Translated\" which is the data type you created a moment ago. That's the data configuration complete.

Step 13. An overview of how this works:-

Each time you perform a Create or Update operation on dynamic data held in Firebase you are first going to add/update that data in the translation collection input field.
This will automatically generate the translations in all your selected locales.
Once the record is created, grab the Reference to the collection and store that value in the collection that contains the text.
For example I have a restaurants collection containing a description field I want translating.... at the point at which I'm creating the record, beforehand, create a document in the \"translations\" table adding the descriptions text to the \"input\" field. Then grab the Document Reference from the output name of the document you just created, and create your restaurant document in the usual way.... except for adding a new field called \"description_ref\" to which you will add the reference from the action output i.e. -> From Variable -> Action Outputs -> [restaurantDescriptionText] (or whatever you name the Action Output) -> DocumentReference.
You now have a reference back to the translations document for your description field as description_ref .
So now when you build the UI you can display the fields from the rest of the restaurant document but in the description text label/field you will add a \"Document From Reference\" query (using Backend Query Button at the very top when you have the text label selected) (and use the description_ref. as the document reference and the \"translations\" collection.
Finally, when entering the variable initial value, you will be selecting from a new menu item in the dropdown (since you added translations to your project) called \"Language Dependent Text\". When you select this it will ask which text you want... so for each locale you have set up, for example German -> translations document -> Get Document Property -> translated -> Data Structure Field -> de. You will have to go through and select the appropriate field for each locale you are supporting which are presented as options when you first select \"Language Dependent Text\".
Hope this helps, sorry if it's a bit lengthy, since this is a No Code platform I've tried to set the appropriate tone but may have missed the mark.
I'm assuming having got this far you'll be able to work out how to update, and delete.
A word of warning, I've no idea if this is the most efficient way, or what the cost implications are, so if these are considerations, maybe seek a professional opinion... which I am not.

Variable Language Translation