Setup Guide Translation for New Devices

Quick answer — A setup guide has to match the app screen by screen, because the customer is holding both. Translate the guide and the app strings together against one glossary, and write to the physical button labels rather than describing them.

Vitra.ai Universe keeps one product vocabulary across box, app, page and video.

The customer is holding two things

During setup the customer has the card in one hand and the phone in the other, and they are comparing them line by line.

That is the only moment in a product's life when two separately translated assets are read simultaneously, and any divergence between them is immediately visible. A step that says "tap Continue" against a button that reads something else in the local build stops the setup dead.

The path, and who owns each leg

Six legs, four owners. Nobody reads the whole path in a target language before launch, which is why the seams are where setup fails.

Write to the label, not around it

If a physical button is silkscreened MODE, the guide should say the MODE button in every language and not translate the word. If it carries a symbol rather than a word, the guide has to describe the symbol consistently — and that description is a glossary entry, decided once. The same applies to LED behaviour. Amber, flashing amber and slow-pulsing amber are three distinct states, and if the local text collapses them into two, the customer cannot tell whether pairing succeeded.

Permissions and network copy

The permission prompts are where localisation quality shows most, because the customer is being asked to grant something and the wording decides whether they do. Mobile app translation handles the strings, but the sequencing has to be checked on a real device in the target language.

Network errors are the other pressure point. A router that rejects the join produces a message the customer has to act on, and a literal translation of a technical string is usually worse than a rewritten one.

Test the whole path

Set the phone to each shipped language and complete setup, once per language, before release.

Most defects found this way are not translation errors at all. They are truncated buttons, a step order that no longer matches, or a screenshot in the guide showing the English UI. Quality control can check the strings; only a walkthrough checks the path.

Keep the corrections in translation memory, so the manual and the support articles inherit the same wording.

First-run content is the start of customer onboarding.

FAQ

Why does setup fail more often in translated markets? Because the customer reads the printed card and the app at the same time, and those are translated by different teams. Divergence that would be invisible elsewhere is immediately visible during setup.

Should button names be translated? Not if they are silkscreened on the hardware. The guide should use the physical label verbatim in every language, and describe symbol-only buttons using one agreed phrase from the glossary.

How should LED states be handled? As terminology. Amber, flashing amber and slow-pulsing amber are distinct states, and collapsing two of them in a target language leaves the customer unable to confirm pairing.

What testing does a setup guide need? A full walkthrough on a real device in each shipped language. It catches truncation, stale screenshots and step-order drift, none of which show up in a string-level review.