Behind the scenes
What TUNED does with each kind of word on its way from the console to a phone. Nothing here needs doing: it is how the system behaves, so you know what to expect.
The path of a change
- You write the words on the Strings page, in English, and if you want in Spanish and Russian.
- A field uses them. A content string reaches users only through a field that uses it: type
@in a reward's name, say, and pick it. Sharing strings need no field, because the app reads them by itself. - The app says the user's language every time it talks to TUNED: the one chosen in the app's settings, or the phone's language by default.
- TUNED sends the words in that language. Spanish to a user who reads Spanish, Russian to a user who reads Russian, and English to everyone else, or wherever the string has no translation in that language.
- The app shows them, on every version of the app, old ones included.
One place holds every string
Every string lives in TUNED's own database with its English text and its translations. The console writes there, and the app and the link pages read from there. UpTop, the rewards partner, holds none of it: a reward named with a string shows in UpTop's own dashboard under its key, not its words.
The user's language
TUNED speaks the language each user reads in. By default that is the language the phone is set to in its system settings, so a new user has nothing to set up. A user can choose another language in the app's settings, and that choice wins over the phone's.
Every time the app talks to TUNED, it says that language. TUNED answers in Spanish or Russian when that is the language, in any regional variety, and in English otherwise.
A push has no app asking at the moment it is sent, so TUNED keeps each user's language from the last time the app was opened. A user who switches to Russian gets Russian pushes once the app has been opened again.
Content words: worded on the way out
When a field uses a string, TUNED swaps the string for its words at the moment it sends the record to a phone, in that user's language. The app only ever receives words, which is why this works on every version of the app. A field in plain text goes out exactly as typed.
- Pushes. A push that uses a string is sent once per language, each in its own words. A push in plain text goes out once, the same for everyone. Once delivered, a push keeps the words it was sent with.
- The Notifications list words each row when the user opens it. Changing a string rewords every row that uses it, including rows for pushes sent earlier.
Sharing words: the app keeps a copy
The app downloads every sharing string in one go, in the user's language, when it opens, whenever it comes back to the front, at most once a minute, and as soon as the user changes language. It keeps the last copy on the phone, so a share works on a bad connection or none, with the words it last received.
When a user shares, the app fills {name} with the name of what is shared. A sharing string that is switched off or can't be used is replaced by the app's own wording for that piece only, so the subject can come from the console while the message falls back, or the other way round.
Link cards are drawn by TUNED's link pages for whichever chat app asks. A chat app asks for a card without saying its reader's language, so a card uses the English text, the shared item's name included. TUNED keeps a card for up to five minutes, and a chat that has already shown a card usually keeps showing it.
Built-in words: shipped, not sent
The app's own words travel inside the app, from one words file with a file per language, and change with a new version. A few fixed sentences live on TUNED's servers instead, such as the automatic pushes, and change once the servers are updated. Built-in words explains how to change or translate them.
How soon a change shows
| What you changed | Users see it |
|---|---|
| A string a token, reward, section or level uses | Within seconds, the next time the screen loads |
| A string a push uses | In the Notifications list on its next load; a push already delivered keeps its words |
| A share's subject or message | The next time the app opens or comes to the front, at most a minute later |
| A link card's text | Within five minutes for a new paste; a card a chat already showed may stay |
| Anything, in the console's own lists and views | On the next load |
| A built-in word | When users update the app, or once the developers' change is live on the servers |
When users see English
English is every string's base text, so users read it:
- When a string has no translation in the user's language. The translation shows as soon as you write it.
- When the user's language is one TUNED doesn't offer, French for instance.
- In link cards, because a chat app asks for a card without saying its reader's language.
Content written as plain text reads exactly as typed, in whatever language you typed it.
Safety nets
- A sharing string that would break is not shown. A text that lost its required
{name}, or picked up a tag the app can't fill, is skipped and the app's own wording shows instead, even if it was saved before the rule existed. - A string in use can't be switched off, and can't be given a tag. The console says where it is used.
- If the strings can't be read, the app keeps the copy it already has. It never throws its words away on a bad answer.
- If a string vanishes between a save and a read, for example when two people edit at once, the user sees nothing in that spot rather than a key, and the console shows the key so an operator can fix it.
Speed
Words are kept in a fast cache, and saving a string clears it, which is why a change shows within seconds. A screen that uses no strings is exactly as fast as before; a screen full of them costs a fraction of a millisecond more.
Related
- Strings and languages — the three kinds of words.
- Built-in words — the words only the developers change.
- Rules and limits — the sharing list, key rules and limits.