Rules and limits
The facts behind Manage strings: the sharing list, key rules, text limits, and who can do what.
The sharing strings
Thirteen fixed strings. A Title or Message must contain {name}, which the app replaces with the name of what is shared. The limits are where the receiving apps cut text off.
| String | Where users see it | Limit |
|---|---|---|
| Token / Reward / Event / Venue / Artist — Title | The subject of the share (an email's subject line; most chat apps leave it out) | 100 characters |
| Token / Reward / Event / Venue / Artist — Message | The message; the link is added after it automatically | 257 characters — fits an X post with the link |
| TUNED link — Preview title | The card's title for a general TUNED link | 60 characters |
| TUNED link — Preview description | The card's description; also used for a shared item that has no description of its own | 155 characters |
| Token — Preview description | The card's description for a shared token | 155 characters |
A shared item's card takes the item's own name as its title. These strings set the general TUNED card, the description of an item that has none of its own, and a shared token's description.
The list is fixed: the app reads exactly these strings, and a new one is added by the developers when the app gains something new to share.
Keys
- Lowercase words made of letters, digits and
_, each starting with a letter, joined by dots:reward.vip.title,wallet.empty_title. - At most 100 characters.
- Never starting with
sharing.— that namespace is the fixed list's. - Unique: two strings can't share a key.
- Never changed after saving.
Texts
| Rule | Manual string | Sharing string |
|---|---|---|
| Length | Up to 2,000 characters | The limit in the table above |
| Tags allowed | Any, written {word} | Only the string's own ({name}) |
| Tags required | None | {name} in a Title or Message |
| Counted how | As written, tags included, an emoji once | Same |
The same rules apply to a Spanish or Russian translation. A translation can be written only once the English text exists.
Fields that take a string
| Record | Fields | Where users see them |
|---|---|---|
| Token | Name | The Tokens tab, the Notifications list, a shared token's card |
| Reward | Name, Description | The Rewards tab, the reward page, My Rewards, a shared reward's card |
| Reward with options | The group's Name, Description | The reward's card, which gathers its options |
| Section | Title, Subtitle | The Rewards tab, and the section's "see all" |
| Level | Name | The level card |
| Level | Push notification | The push a user gets on reaching the level |
| Notification | Title, Message | The push, a test push, the Notifications list |
A field can point only at a manual string that is Active, Set, and has no tags. Locations, groups and events take plain text only.
Who can do what
| Role | Strings page |
|---|---|
| Owner, Admin | Read, add, edit, translate, switch |
| Any signed-in operator | Pick a string in an @ field |
Timing
| Change | Shows |
|---|---|
| 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 and message | The next time the app opens or comes to the front, at most a minute later |
| A link card in a chat app | Up to five minutes for a new link; a link already pasted keeps its card |