Why you should focus on iOS Localization

More documents

Recommendations

Info

<strong>Why</strong> You Should Focus On iOS Localization <strong>Why</strong> IOS Localization? Now let’s get down to the nitty-gritty. If <strong>you</strong>’re ready to start the app localization process, how do <strong>you</strong> decide whether to localize for Android or iOS? <strong>Why</strong> <strong>should</strong> <strong>focus</strong> on iOS localization? In an ideal world, <strong>you</strong>’ll carry out <strong>you</strong>r mobile app localization for both platforms. You’ll share data between iOS and Android and corner the market of smartphone users globally. But since we don’t live in an ideal world, <strong>you</strong> may find <strong>you</strong>rself faced with a little stumbling block called a budget. Sometimes <strong>you</strong>’ll have a team of developers who prefer iOS to Android. Maybe <strong>you</strong> have a personal preference for it, or <strong>you</strong>r research tells <strong>you</strong> that more of <strong>you</strong>r customer base uses iOS devices. Whatever the situation, there are several good arguments for <strong>focus</strong>ing on iOS localization. Let’s check them out… IOS Localization Is Easier If <strong>you</strong>’re on a budget or time crunch, iOS localization is a lot easier. OK, so it’s always wise to prepare <strong>you</strong>r app for localization for both platforms from the start, to avoid unnecessary hassles later on. If <strong>you</strong> create <strong>you</strong>r strings only for <strong>you</strong>r iOS app, all <strong>you</strong>r careful preparation will be useless later on, when <strong>you</strong> want to use the files for Android. So, localize for iOS, but don’t close the door on Android. But, Apple’s latest update, iOS 10, was practically designed with localization in mind. With at least five massive updates that make localizing for iOS even easier: 1 Keyboard is multilingual This is awesome news for developers and users alike, as iOS 10 lets <strong>you</strong> use a multilingual keyboard. Instead of having to change languages using the globe icon, <strong>you</strong> can type straight into the keyboard in any of the languages <strong>you</strong> selected in <strong>you</strong>r settings. You will automatically get the relevant autocorrect function for the language <strong>you</strong> type in. Pretty neat, hey? phraseapp.com | sales@phraseapp.com | +49-40-357-187-76 | twitter.com/phraseapp | facebook.com/phraseapp | linkedin.com/company/phraseapp
<strong>Why</strong> You Should Focus On iOS Localization 2 Localized Number Pads As <strong>you</strong> know by now, mobile app localization goes way beyond just words. Units of measurements and numbers are important too. With iOS 10, the number pads are now localized as well. This is great for phone numbers, credit card numbers, and IP addresses. Just use UIKeyboardTypeASCIICapableNumberPad as the keyboard type and the rest is easy. 3 iOS 10 Loads the Right Language for the Right User Localization is a complex process. If <strong>you</strong> only had to deal with the major different languages, like Spanish, French and German, it would be a piece of cake. But languages vary from region to region. British English is not the same as American English. Castilian Spanish varies from the Colombian dialect. They have different spellings, grammar and vocabulary. But, thanks to Apple’s latest update, <strong>you</strong> don’t have to worry about localizing <strong>you</strong>r app into hundreds of thousands of languages variations. The latest preferredLocalizations bundle from iOS helps ensure that <strong>you</strong> deliver the best possible localized version to <strong>you</strong>r users. How? Imagine <strong>you</strong> have an English-Speaking user in India and <strong>you</strong>r app isn’t localized into Indian English. Apple’s bundle will recognize that <strong>you</strong>r user prefers Indian English but that <strong>you</strong> don’t have it available. It will then deliver the next best option, which in this case, would be British English. Not only does this speed up <strong>you</strong>r iOS localization process, but it reduces the cost of localizing for thousands of different regional variations. 4 XCode 8 Updates The latest updates to XCode 8 work like a safety net to catch <strong>you</strong> from making errors during <strong>you</strong>r iOS localization. There are two new settings in XCode 8, called static analyzer settings. You can work more easily and be notified if any information is missing. Turn on the “Missing Localizability” setting, and if <strong>you</strong> forget to use <strong>you</strong>r NSLocalizedString, <strong>you</strong>’ll be alerted with a warning. Similarly, as the name suggests, with the “Missing Localization Context Comment,” <strong>you</strong>’ll be notified if any comments are missing. Any better and Apple will do the job for <strong>you</strong>! 5 Improved Formatters Oftentimes, formatters like date, weights, times, etc. can cause the greatest problems when localizing. For example, the Chinese date format is year-month-day. So, when <strong>you</strong> have <strong>you</strong>r formatters correct in <strong>you</strong>r base language, using a fixed format, this can cause hiccups when it phraseapp.com | sales@phraseapp.com | +49-40-357-187-76 | twitter.com/phraseapp | facebook.com/phraseapp | linkedin.com/company/phraseapp
Page 1 and 2: Why You Should Foc
Page 5: Why You Should Foc

Why you should focus on iOS Localization

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?