Strings and languages
Every word a user reads in TUNED is one of three kinds. The kind decides who writes and translates it, and how a change reaches users.
The three kinds of words
| Built-in words | Content words | Sharing words | |
|---|---|---|---|
| What they are | TUNED's own words, the same for every user | The words of something you create in the console | The words the app adds when a user shares something |
| Examples | Add funds, Claim Reward, an error message | A reward's name and description, a token's name, a push's message | A share's subject and message, the card under a pasted TUNED link |
| Who changes them | Anyone, in the app's words file; the developers ship it | You, on the record or on the Strings page | You, on the Strings page |
| How soon | With the next app version | Within seconds | The next time the app opens, at most a minute later |
| Translated by | A translator or an AI tool, from the same file | You, on the Strings page, when the field uses a string | You, on the Strings page |
Built-in words
Every button, label, heading, hint, error and empty screen in the app: nearly 900 texts, from Create an Account on the welcome screen to the message under an empty wallet. They are kept in one file, each with a note saying where it shows, so a copywriter, a translator or an AI tool can reword or translate them. The developers put the file into a new app version, which users get when they update.
A few fixed sentences come from TUNED's servers instead: the automatic pushes such as You earned tokens and On its way, the sign-up code email and text message, and the page a shared link opens in a browser. The developers change those, without an app update.
Built-in words explains the file, how to change or translate it, and lists the server sentences.
Content words
The words of the things you create in the console. Users read them on the Tokens and Rewards tabs, on the level card, and in pushes.
| What you create | Fields with content words |
|---|---|
| A token | Name |
| A reward | Name, description |
| A section on the Rewards tab | Title, subtitle |
| A level | Name, push notification |
| A push | Title, message |
Each of these fields takes its words in one of two ways:
- Plain text, typed into the field. Every user reads exactly what you typed, whatever their language.
- A string, picked by typing
@in the field. The words then live on the Strings page, where they can be translated into Spanish and Russian and changed in one place for every field that uses them. The Strings page lists these strings as Manual.
Event, venue and artist names and descriptions are content too. They come from the event sources and show as published.
Sharing words
When a user taps Share on a token, a reward, an event, a venue or an artist, the app proposes a subject and a message, and adds the link after the message. When someone pastes a TUNED link into WhatsApp or iMessage, the chat shows a card with a title and a short description. Those are sharing words.
They are a fixed list on the Strings page, of the type Sharing. You rewrite them, translate them and switch them off; the list itself is fixed, because the app reads exactly these. Each subject and message must contain {name}, which the app fills in with the name of what is shared. If one is switched off, the app uses its own wording instead, so a share is never empty.
Which kind is a word?
| If the word is… | It is a… | Change it |
|---|---|---|
| On a button, a label, a heading, an error or an empty screen | Built-in word | In the app's words file |
| In an automatic push, like You earned tokens | Built-in word | Send it to the developers |
| The name or description of a token, reward, section or level | Content word | On the record, or on its string |
| In a push you send from the console | Content word | When you write the push |
| The subject or message of a share, or the text of a link card | Sharing word | On the Strings page |
| The name or description of an event, a venue or an artist | From the event sources | At the event source |
Languages
- The phone's language by default. TUNED starts in the language the phone is set to, so a new user has nothing to set up.
- The user can choose. A user can pick another language in the app's settings, and TUNED uses that choice from then on, on every screen and in every push.
- English is the base. Every string has an English text. Spanish and Russian are translations, written per string.
- A missing translation shows English. Nothing breaks while a translation waits.
- Any other language reads English. A user whose language TUNED doesn't offer, French say, reads TUNED in English. Any Spanish or Russian counts, so a phone set to Mexican Spanish reads Spanish.
All three kinds follow the user's language. Adding a language, French say, is a small change for the developers, after which you write the French for content and sharing words, and the app's words file is translated into French and shipped with a new app version.
Who changes what
In the console, with no app update:
- Content words, written and translated on the Strings page when the field uses a string: a token's name, a reward's name and description, a section's title and subtitle, a level's name and push notification, a push's title and message.
- Sharing words: the subject and message for sharing a token, a reward, an event, a venue and an artist, and the link card texts.
With a new app version:
- Built-in words and their translations, in the app's words file. Anyone can reword or translate the file — a copywriter, a translator or an AI tool — and the developers ship it.
The developers:
- The sentences on TUNED's servers, such as the automatic pushes, and their translations.
- A new sharing string, when the app gains something new to share.
The event sources:
- Event, venue and artist names and descriptions.
Related
- Manage strings — add, write, translate and use strings, step by step.
- Behind the scenes — how each kind of word reaches a phone, and how soon.
- Built-in words — the words only the developers change.
- Glossary — the words the console uses.