Writing or translating for Mobile

I’m constantly approached by developers working on new Mobile apps and by translators working on the localization of existing mobile apps asking me for guidelines and best practices on how to write or translate for Mobile. I’ve given the topic a lot of thoughts and I come out with the 3 magic Fs rule: No, the 3 Fs don’t stand for Francesco, Francesco and Francesco; they stand for Fast, Focus and Fun.

When writing for mobile, keep in mind the intended audience: mobile users have less time and shorter attention spam than regular web users. And they want to have fun. So here it goes:

1. Fast: Keep it brief. Be concise and precise. Try to use the same number of characters as in the English source (including spaces), and don’t use more unless absolutely necessary. Describe only what’s necessary, and no more. Don’t try to explain subtle differences. They will be lost on most users.

2. Focus: Keep it simple. Pretend you’re speaking to someone who’s smart and competent, but doesn’t understand technical jargon. Use short words, active verbs, and common nouns. Put the most important thing first. The first words in a sentence should include at least a hint of the most important information in the phrase.

3. Fun: Be friendly. Talk directly to the reader using second person “you”*. If your text doesn’t read the way you’d say it in a casual conversation, it’s probably not the way you should write it. Don’t be abrupt or annoying. Make the user feel safe, happy and energized. Don’t use abbreviations to shorten a word or a phrase. Abbreviations as a shortcut for space restrictions must be avoided at all times.

Examples:

1. Keep it brief.

Too formal
Consult the documentation that came with your phone for further instructions.

Preferred
Read the instructions that came with your phone.

2. Keep it simple.

Confusing
You cannot perform this action with this app because this feature is not supported for your country. Please use the main website instead.

Crystal clear
This feature is not supported in your country yet. Please use the website.

3. Be friendly.

Confusing
Sorry! The app is not responding. Please close it and reopen it.

Shorter, more direct, no fake apologetic
The app isn’t responding. Please restart.

4. Put the most important thing first.

Task last
Tap Next to complete setup.

Task first
To complete the setup, tap Next.

5. Describe only what’s necessary, and no more.

Too wordy
The app needs to communicate with our servers to sign in to your account. This may take a few moments.

Short and to the point
The app is connecting to the server. This can take a few moments.

6. Don’t use abbreviations to shorten a word or phrase

Abbreviation
Go to Intl. settings.

Spelled out
Go to International settings.

Being fast means that features are fast to use, therefore the text needs to be fast to read. Focus is about simplicity, therefore the text needs to be easy to read. Fun is about engagement, therefore text needs to be friendly.

Italian Literary Translators

The Italian Literary translators are struggling. Please help them by signing this petition.

Here you can find an interesting interview (in Italian) to Marina Pugliano, Yasmina Melouah and other Italian Literary translators:

Translation quality: what is it?

Try to ask this question to several stakeholders and you would be surprised about how many different answers you will get.

Some may say that quality is measured by the user experience and that a quality localized product is one that functions the same way as the English version.

Others may say that a quality translation is one that maintains brand consistency.

Or that a quality translation is one that is factually accurate, readable and (hear hear) not localized (preserves the source culture nuances).

I find all the above answers valid.

However, in June 2006 a new translation quality assurance standard was published by ASTM International and unfortunately it’s still relatively unknown: ASTM F2575.

The ASTM translation standard (F2575) defines translation quality as:

The degree to which the characteristics of a translation fulfill the requirements of the agreed upon specifications

This definition implies two stages: Agreeing upon project-specific specifications and applying those specifications. Sounds too easy, doesn’t it? But it actually works! This approach can be applied to every translation project.

How? Well, translation projects usually consist of three phases:

Pre-Production, Production and Post-Production (aka Post Mortem).

It’s in the Pre-production phase when you should discuss and agree upon the specifications. In the Production phase, these specification should be applied. Finally, in the Post-Production phase, you should carry out the project analysis to verify the fulfillments of the agreed upon specifications.

If all translation projects followed this simple approach, all the different stakeholders would be much happier at the end of the project!