Hardships of Mobile Localization in a Desktop World Pavel Simsa Avaya

Agenda Some General Intro Mobile Development Issues Mobile Localization Issues Mitigations Q & A

Quick check How many of you have: – A smartphone? – iPhone? – BlackBerry? – Windows Phone? – Some Android? – Some Symbian? – Something else?

Why “Desktop world?” Desktop Mature Standardized Tools and processes Community support Infinite functionality Mobile Relatively young Fragmented Lack of tools Limited community Strictly limited functionality

Simple Comparison Desktop 3 Operating Systems Rest is Irrelevant Mobile 100 Different Mobile Stores 1000 Mobile Operators 15 Mobile Platforms 100 Device Manufacturers

Problems and differences Development Localization Deployment and Testing Publishing

Desktop Development, the Good Start of everything Standards Easy deployment and selfhosting Runs where developed Easy access to devices Great functionality availability

Desktop Development, the Bad Legacy issues Distribution channels Varying application quality

Mobile Development, the Good More international-ready at the start Good foundation Mature development tools Easy to release Quality standards

Mobile Development, the Bad Very fragmented Migrated tools and processes Limited form factor Limited functionality High customer expectations Difficult pre-release deployment

Very Fragmented… Different screen sizes Input method availability Available connection type and speed Carrier customizations Device and OS-specific limitations

Mobile Development, the Bad Very fragmented Migrated tools and processes Limited form factor Limited functionality High customer expectations Difficult pre-release deployment

Internationalization (i18n) Most standard issues as on desktop Additional issues More likely to occur Aggravated

Localization Same process, different tools Platform support Linguistic differences Translators’ reference Resource limitations

Deployment and Testing Limited deployment channels Testing platform choice Testing automation Handset-specific features

Publishing

What do we do? Change your mindset Mobile device is not a small desktop

Before development starts Good specs Per-platform variances Standards and criteria Detailed plan Flexible schedule

Before localization starts Plan and schedule Tools and technologies Translation resources and process QA and testing strategy

The Execution Stick to the plan Know your OS No shortcuts Keep it short And remember: Mobile is not a small desktop.

Q & A?

Good luck!