Import & Content
Card translation
Fill the back of a card with a suggested translation from Apple Translation, then Audiofirst's server, or type it yourself.
What it does
Auto-translate fills one side of a card with a suggested translation of the other side. The app tries Apple’s Translation feature first (iOS 18 or later). If that cannot be used or returns nothing, it asks Audiofirst’s server. If that fails too, you type the translation yourself. It runs only when you tap the button, for one card side at a time.
How to use it
- Open the card editor of a pack you created. See Create a pack.
- Tap the plus button (Add card), or tap a card in the list.
- Type the text in Front (prompt).
- Tap Auto-translate under Back (answer). Once the back has text, the button reads Regenerate.
- Wait until the spinner stops. A small note under the button names the source: “Translated on-device (Apple)” or “Translated via remote model”.
- Read the text in Back (answer) and correct it.
- Tap Done.
Settings that affect it
- Settings → Language Learning → I’m learning — default: en-US. This is the language of the front text, the source of the translation.
- Settings → Language Learning → I speak — default: Follow phone system. This is the language the back is translated into.
- Settings → Language Learning → Show translations — default: on. It controls whether translations appear on cards. The footer says: “Translations appear on cards when available for your native language.”
Limits and honest caveats
- The result replaces any text already in Back (answer).
- The button stays disabled while Front (prompt) is empty.
- Apple’s Translation feature is used first, and only on iOS 18 or later. The app labels that route “Translated on-device (Apple)”.
- If Apple’s route is not available, or gives no text, the app sends a request to Audiofirst’s server, the same server address that serves cloud voices. The request holds the text of the side you are translating and the two language codes. When you are signed in, it also carries your sign-in token. The request has a 10-second timeout.
- The app code does not show how the server produces the translation, so this manual does not say whether an AI model does it. It also does not show what the server keeps.
- If both routes fail, the note reads “Auto-translate unavailable — enter manually.” and the back stays as it was.
- Treat the result as a suggestion. Check it before you save the card.
- The app translates one card side per tap. It has no button that translates a whole pack.
- The two notes above are shown in English in every interface language.
- The card editor opened from a photo or screenshot import has its own translate buttons for both the front and the back, with a language menu for each side. Those translate buttons and their notes are in Russian in every interface language. See Draft review.
FAQ
Does Auto-translate work offline?
The app labels the Apple route “on-device”. The server route needs a network connection. If neither works, you type the text yourself.
Where does my text go?
If Apple’s route is used, the app hands the text to Apple’s Translation feature. If the server route is used, the text and the language codes go to Audiofirst’s server, as described above. The in-app AI disclosure describes other transfers. See AI disclosure.
Which language pairs are supported?
The app code does not list pairs. It asks Apple’s Translation feature, then the server, for the pair set by I’m learning and I speak. If neither returns text, you get the manual-entry note.
Is the translation made by AI?
The app code does not say. It shows only that the app asks Apple’s Translation feature and then Audiofirst’s server.
How do I store a translation on a card?
In the card editor, turn on Add translation. Enter a Locale (e.g. ru-RU), then Translated prompt and Translated answer. A translation is saved with the card only when the locale has a value and at least one translated field has text. The footer says it is “Shown alongside the card for language-learning packs.”