# Translating Your App

In order to dynamically change the language on each page in the editor without using an external service, we can use what Bubble calls “App Text”.  

In summary, for any text you need to translate on a page, you would first click on that element, and replace the static text with “App Text”.  Here is Step 1 of that process:<br>

{% embed url="<https://www.useloom.com/share/966ab7dbecee4f00b908ace90e409213>" %}

Once you’ve defined an App Text, and labeled it, it will appear in the **Settings —> Language** tab. From there, you can edit it in different languages (you have to manually enter each translation).  By default the input will be empty after you select a different language from the dropdown; then you can add that ‘translated’ version of that App Text in the App Settings tab for each language you prefer (shown below):

{% embed url="<https://www.useloom.com/share/01317e15aad94b13a477cde9885e4f93>" %}

{% hint style="info" %}
Note: There is no ‘save’ button; the editor will save these translations automatically
{% endhint %}

Once you’ve defined these App Texts in the editor, the texts will be automatically translated into the language that the Current User has selected on their account page. Please note that when you are displaying dynamic information (something a User typed in their language and is saved to the database) and those texts need to be translated, you will want to use the Google Translate API for those texts.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.littlebaytech.com/templates/messaging-template/page-guides/translating-your-app.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.