Affordable and efficient multi platform localisation. case study
•
0 likes•47 views
This document discusses localization strategies for multi-platform apps. It defines internationalization as making an app adaptable to different languages and cultures, while localization is the process of translating an app into multiple languages. For Android and iOS, it recommends using the same keys for strings to simplify and reduce the cost of localization. The document also provides tips for effective localization like using formatters instead of string concatenation and choosing a translation service that provides fast, high-quality translations by native speakers at an affordable price.
Report
Share
Report
Share
Recommended
AIM | HDC 2016 Globalization As a Service
The talk will not only provide a case study of how Hudl tackled the globalization challenge across our platforms (iOS, Android, Web), but will also provide tips and tricks on testing, reliability, and the translation process. In this talk I will cover the following:
- How to start with an MVP (minimum viable product) on globalization
- How globalization fits in a microservice architecture
- How to make globalization scalable inside your organization when there are many parties involved.
If you are a software engineer, quality engineer, quality analyst, or product manager this session will be helpful if you are thinking about internationalizing. In addition, if you are already working with an internationalized product we invite you to attend as this will provide a different engineering, process, and testing angle.
For more info please visit bit.ly/z481516
Affordable and efficient multi platform localisation. case study
This document discusses strategies for making multi-platform localization affordable and efficient. It compares internationalization vs localization and the approaches for Android vs iOS. It provides tips for preparing assets for localization including using formatters instead of concatenation and ensuring consistent keys. Finally, it shares lessons from the author's experience localizing mobile apps and cloud services.
Mobile Cafe #6
This document discusses strategies for making multi-platform localization affordable and efficient. It covers the differences between internationalization and localization, considerations for Android vs iOS localization, best practices for preparation including using formatters instead of concatenation, and lessons from the author's experience localizing multiple apps and platforms.
MVP Virtual Conference - Americas 2015 - Cross platform localization for mobi...
This document discusses cross-platform localization for mobile apps using .NET. It introduces Xamarin, a tool that allows developers to write native mobile apps for Android and iOS using C# and shared code bases. It also discusses the Multilingual App Toolkit, which helps manage localized string resources across platforms. Localization involves translating text, images, and other resources to support multiple languages and locales. The document provides tips on effective localization strategies and managing localized resources in Xamarin, Xamarin.Forms, Android and iOS apps.
Which Language Is Best For iOS App Development.pdf
The document discusses programming languages for iOS app development, including Swift, React Native, and Xamarin. Swift is Apple's primary language and offers a simple syntax, open source framework, and fast performance. React Native is good for cross-platform apps, offering a single codebase, open source components, and quick refresh of code changes. Xamarin uses C# and the .NET framework to build apps for multiple platforms but has less popularity and slower updates than other options. Each language has strengths and weaknesses depending on the app requirements. The document provides a comparison of the languages and recommends evaluating your specific needs when choosing a language.
MyAppconverter platform mappings
MyAppConverter is a powerful service that helps developers convert native iOS mobile apps instantly to native Android app, it's not focused mainly on the look and feel, and UI interaction of your app. That means we don't replicate your application as it is. Instead, MyAppConverter make all changes to make a project suitable for the development of an Android application.
MyAppConverter currently support only iOS to Android conversion and objective-c to swift.
Mobile Delivery Run Through
This document discusses options for building mobile applications and presents Ionic Framework as a solution. It notes that building native mobile apps for multiple platforms is difficult due to different styles, code bases, teams required. It considers building fully native, compiling to native, and using web technologies. While building native has highest fidelity and performance, it has downsides of multiple languages/teams. Compiling to native has cross-platform UI but is not truly native. The document argues that using web technologies like Ionic Framework is easier and future-proof, giving developers access to native device capabilities through plugins. Ionic provides pre-built UI components, gestures, animations for a native look on each platform while developing with open web standards.
Beyond English - Make Your Android App a Global Success
This document discusses strategies for making an Android application globally successful by supporting localization. It covers concepts like internationalization and localization, ISO language and country codes, the layout of an Android project to support localization including folder naming conventions, how Android locates localized resources based on user locale and configuration qualifiers, and tools to help with localization testing and publishing localized apps on the Android Market. The presentation agenda includes topics on globalized application concepts, Android runtime support, localization tools, best practices, and a terminology section defining terms like internationalization, localization, and configuration qualifiers.
Recommended
AIM | HDC 2016 Globalization As a Service
The talk will not only provide a case study of how Hudl tackled the globalization challenge across our platforms (iOS, Android, Web), but will also provide tips and tricks on testing, reliability, and the translation process. In this talk I will cover the following:
- How to start with an MVP (minimum viable product) on globalization
- How globalization fits in a microservice architecture
- How to make globalization scalable inside your organization when there are many parties involved.
If you are a software engineer, quality engineer, quality analyst, or product manager this session will be helpful if you are thinking about internationalizing. In addition, if you are already working with an internationalized product we invite you to attend as this will provide a different engineering, process, and testing angle.
For more info please visit bit.ly/z481516
Affordable and efficient multi platform localisation. case study
This document discusses strategies for making multi-platform localization affordable and efficient. It compares internationalization vs localization and the approaches for Android vs iOS. It provides tips for preparing assets for localization including using formatters instead of concatenation and ensuring consistent keys. Finally, it shares lessons from the author's experience localizing mobile apps and cloud services.
Mobile Cafe #6
This document discusses strategies for making multi-platform localization affordable and efficient. It covers the differences between internationalization and localization, considerations for Android vs iOS localization, best practices for preparation including using formatters instead of concatenation, and lessons from the author's experience localizing multiple apps and platforms.
MVP Virtual Conference - Americas 2015 - Cross platform localization for mobi...
This document discusses cross-platform localization for mobile apps using .NET. It introduces Xamarin, a tool that allows developers to write native mobile apps for Android and iOS using C# and shared code bases. It also discusses the Multilingual App Toolkit, which helps manage localized string resources across platforms. Localization involves translating text, images, and other resources to support multiple languages and locales. The document provides tips on effective localization strategies and managing localized resources in Xamarin, Xamarin.Forms, Android and iOS apps.
Which Language Is Best For iOS App Development.pdf
The document discusses programming languages for iOS app development, including Swift, React Native, and Xamarin. Swift is Apple's primary language and offers a simple syntax, open source framework, and fast performance. React Native is good for cross-platform apps, offering a single codebase, open source components, and quick refresh of code changes. Xamarin uses C# and the .NET framework to build apps for multiple platforms but has less popularity and slower updates than other options. Each language has strengths and weaknesses depending on the app requirements. The document provides a comparison of the languages and recommends evaluating your specific needs when choosing a language.
MyAppconverter platform mappings
MyAppConverter is a powerful service that helps developers convert native iOS mobile apps instantly to native Android app, it's not focused mainly on the look and feel, and UI interaction of your app. That means we don't replicate your application as it is. Instead, MyAppConverter make all changes to make a project suitable for the development of an Android application.
MyAppConverter currently support only iOS to Android conversion and objective-c to swift.
Mobile Delivery Run Through
This document discusses options for building mobile applications and presents Ionic Framework as a solution. It notes that building native mobile apps for multiple platforms is difficult due to different styles, code bases, teams required. It considers building fully native, compiling to native, and using web technologies. While building native has highest fidelity and performance, it has downsides of multiple languages/teams. Compiling to native has cross-platform UI but is not truly native. The document argues that using web technologies like Ionic Framework is easier and future-proof, giving developers access to native device capabilities through plugins. Ionic provides pre-built UI components, gestures, animations for a native look on each platform while developing with open web standards.
Beyond English - Make Your Android App a Global Success
This document discusses strategies for making an Android application globally successful by supporting localization. It covers concepts like internationalization and localization, ISO language and country codes, the layout of an Android project to support localization including folder naming conventions, how Android locates localized resources based on user locale and configuration qualifiers, and tools to help with localization testing and publishing localized apps on the Android Market. The presentation agenda includes topics on globalized application concepts, Android runtime support, localization tools, best practices, and a terminology section defining terms like internationalization, localization, and configuration qualifiers.
Mobile application development platform
The document discusses and compares several popular mobile application development platforms (MADPs), including Kony App Platform, Android Studio, Apple Xcode, Appcelerator, Kinvey, Appzillon, and Microsoft's Xamarin. For each platform, it outlines their key features and capabilities, pros, and cons. The platforms vary in their support for native or cross-platform development, programming languages used, ease of use, documentation, and other factors.
Bringing the Ruby language into the mobile world
Presentation given at RubyWorld 2014 (Matsue, Japan), a business conference about the Ruby programming language. Slides in Japanese / English.
Sample code: https://github.com/lrz/rubymotion-hybrid-sample
Internationalisation In Rails
This document discusses internationalization and localization in Ruby on Rails. It defines internationalization (i18n) as making an application support multiple languages without code changes, and localization (L10n) as adapting an application for a specific region or language. The document then explains how Rails version 2.2 introduced the I18n gem to provide easy internationalization capabilities out of the box like translating text and formatting dates and times for different locales. It also provides a brief overview of how the I18n features work in Rails.
MyAppConverter DroidconUK 2014
MyAppConverter presentation at Droidcon UK - October 2014.
We are building the the world’s first true native to native mobile code converter.
[Srijan Wednesday Webinars] Building Full-Fledged Native Apps Using RubyMotion
Speaker: Laurent Sansonetti
This webinar takes us through RubyMotion, an app development environment that helps you build native apps using the Ruby language. We take a look at how RubyMotion works internally, how it’s different for other mobile toolchains and how we can build cross-platform apps with it.
The session also presents a live demo of Flow, that let's you access both iOS and Android APIs on one single codebase, making it extremely easy to build cross-platform apps.
Internationlization
This document discusses internationalization and localization. Internationalization is the process of making applications adaptable to different languages and regions, while localization is the process of translating an application for a specific locale. Reasons for internationalization include differences in language, currency, and date/time formats across locales. The document outlines internationalization elements like captions, dates, numbers, percentages that require formatting. It also discusses the Unicode standard, use of properties files and ResourceBundles for localization, Locale class for specifying locales, and MessageFormat for variable text formatting.
Appium - Reality check on the world’s leading Open Source Framework for Mobil...
Appium is clearly the world leading framework for mobile apps test automation. Adoption of Appium is in constant rise, and for the good reasons.
Yet, in many cases those who do their initial steps or even progressing with the framework realize that the world is not that simple, challenges arise, limitations are discovered and one can find himself wondering whether the right decision was taken in investing the time and money into it (yes... open source cost you money).
In this talk we will pause for a while, review why Appium is an outstanding framework, while also do a reality check of the cons and pros of Appium, helping you make the best out of it, or at least have a clear understanding of what's ahead of you.
Pender presentation 2.0
Lorin Beer's presentation from the SF PhoneGap Meetup on November 28, 2012. Pender is a cross platform library which offers hardware accelerated graphics through a Canvas API on mobile devices.
Mono for Android... for Google Devs
The document summarizes a presentation given by Craig Dunn on Mono for Android at a Google Developer Group meeting. It discusses how Mono for Android allows developers to build Android applications using C# in MonoDevelop or Visual Studio. It also covers how code can be reused across Android, iOS, and Windows platforms. The presentation included demos of building a simple Android app in C# and examples of cross-platform apps developed with Mono.
The Ring programming language version 1.5.1 book - Part 4 of 180
This document summarizes Ring, an innovative programming language designed to be simple, small, flexible and fast. Key features include a hybrid compiler and virtual machine, declarative and natural language programming, compact syntax without semicolons, first class variables, lists, objects and functions, automatic memory management, and cross-platform support. The language aims to provide high productivity for tasks like rapid application development, scripting, and building visual programming tools.
Introduction to xamarin
Xamarin enables developers to write mobile apps using C# and share code across platforms like iOS and Android. Developers can build native user interfaces and take advantage of native performance on each device, while sharing up to 90% of their code. This hybrid approach allows building apps for over 2.5 billion devices using C# and the .NET framework in Visual Studio. Key benefits include writing everything in C#, 100% API coverage on all platforms, and always being up to date with the latest APIs.
Internationalization in Angular Presentation
Internationalization, sometimes referenced as i18n, is the process of supporting multiple languages in our applications. In this session, we will demonstrate how we can enable our angular application to target any language in the world using ngx-translate.
Introduction to Xamarin Development
This document discusses cross-platform mobile app development using Xamarin. It introduces Xamarin, which allows developers to write native mobile apps in C# that can target iOS, Android, and Windows platforms, while sharing common code. The document compares different cross-platform approaches like silo, HTML5, and Xamarin. It also provides information on Xamarin licensing options for students.
Once CODE to rule them all
This document discusses using domain specific languages (DSLs) to help address challenges in developing mobile applications for multiple platforms. It introduces the Applause framework, an XText-based DSL for creating mobile apps, which uses code generation to produce applications for iOS and Android from a single codebase. An example SASSI Pocket Guide app is demonstrated to show how concepts like entities, views and navigation are mapped to the DSL and then generated to native mobile platforms.
Introduction to xamarin
Xamarin enables developers to write native mobile apps in C# that can run on iOS, Android, and Windows platforms. It allows code-sharing so the majority of the code can be shared across platforms while maintaining native user interfaces and performance. Key benefits include writing apps once in C# and deploying to over 2.5 billion devices, near 100% API coverage on all platforms, and leveraging Visual Studio and .NET frameworks for development.
Comparisons react native vs. flutter vs. ionic vs. xamarin vs. native script
When it comes to mobile app development, one can choose between fully native and cross-platform applications. Both approaches have their own unique advantages. This topic will provide you with a comparison of some of the most popular app development frameworks – 5, to be exact. These include React Native, Flutter, Xamarin, NativeScript, and Ionic.
The Ring programming language version 1.5.2 book - Part 5 of 181
This document provides an overview of the Ring programming language. It discusses the motivation for creating Ring, which was to build a new version of Programming Without Coding Technology software from scratch using a single language. Ring aims to be innovative, practical, simple, small, flexible and fast. It supports multiple programming paradigms and can be used to create various application types. The document outlines Ring's features, which include its hybrid compiler/virtual machine implementation, declarative programming support, natural language programming, portability and more. It is open source under the MIT license.
Cross platform mobile approaches
This document discusses cross-platform mobile development. It defines cross-platform development as developing applications that can run on multiple platforms simultaneously. The document then explores different cross-platform approaches like web apps, hybrid apps, interpreted apps, cross-compiled apps, and generated apps. It provides details on how each approach works and when they are involved in the development process. The document also compares the different approaches based on factors like native access, performance, cost, and tools. It concludes that cross-platform options are not fully mature but can be good choices for prototypes, existing web apps, or as a shortcut to the market.
The Ring programming language version 1.10 book - Part 6 of 212
This document provides an overview and history of the Ring programming language. It discusses the motivations for creating Ring, which was to have a dynamic, small, and productive language for building applications and development environments. Ring draws influence from languages like Lua, Python, Ruby, C, C#, and BASIC. The document outlines the language's features, which include support for declarative and natural language programming, flexibility in syntax, portability across platforms, and automatic memory management.
The Great Mobile Debate: Native vs. Hybrid App Development
It’s not easy being a mobile developer. iOS and Android dominate the market, Windows Phone is climbing into third place, and we’re not really sure if BlackBerry still matters. Do you focus on one platform or many? What size of the mobile population do you really want to reach? Each mobile platform comes with its own programming languages, SDKs, IDEs and application lifecycle & architecture. Are we really expected to learn all of this? Isn’t HTML5 supposed to be the Silver Bullet so we can finally write apps once and run them everywhere? This session will demystify all these questions, walking you through the modern mobile ecosystem, and explore your options as a developer. We’ll review the native story on each major platform, discuss the pros & cons of both mobile native and web development, cover some of the cross-platform solutions available to developers, and explore best practices and guidelines to insure a successful mobile strategy. Don’t just blindly pick a side or assume that “one size fits all”, this session covers one of the most hotly contested debates in modern IT. Come join us and be a part of the conversation.
More Related Content
Similar to Affordable and efficient multi platform localisation. case study
Mobile application development platform
The document discusses and compares several popular mobile application development platforms (MADPs), including Kony App Platform, Android Studio, Apple Xcode, Appcelerator, Kinvey, Appzillon, and Microsoft's Xamarin. For each platform, it outlines their key features and capabilities, pros, and cons. The platforms vary in their support for native or cross-platform development, programming languages used, ease of use, documentation, and other factors.
Bringing the Ruby language into the mobile world
Presentation given at RubyWorld 2014 (Matsue, Japan), a business conference about the Ruby programming language. Slides in Japanese / English.
Sample code: https://github.com/lrz/rubymotion-hybrid-sample
Internationalisation In Rails
This document discusses internationalization and localization in Ruby on Rails. It defines internationalization (i18n) as making an application support multiple languages without code changes, and localization (L10n) as adapting an application for a specific region or language. The document then explains how Rails version 2.2 introduced the I18n gem to provide easy internationalization capabilities out of the box like translating text and formatting dates and times for different locales. It also provides a brief overview of how the I18n features work in Rails.
MyAppConverter DroidconUK 2014
MyAppConverter presentation at Droidcon UK - October 2014.
We are building the the world’s first true native to native mobile code converter.
[Srijan Wednesday Webinars] Building Full-Fledged Native Apps Using RubyMotion
Speaker: Laurent Sansonetti
This webinar takes us through RubyMotion, an app development environment that helps you build native apps using the Ruby language. We take a look at how RubyMotion works internally, how it’s different for other mobile toolchains and how we can build cross-platform apps with it.
The session also presents a live demo of Flow, that let's you access both iOS and Android APIs on one single codebase, making it extremely easy to build cross-platform apps.
Internationlization
This document discusses internationalization and localization. Internationalization is the process of making applications adaptable to different languages and regions, while localization is the process of translating an application for a specific locale. Reasons for internationalization include differences in language, currency, and date/time formats across locales. The document outlines internationalization elements like captions, dates, numbers, percentages that require formatting. It also discusses the Unicode standard, use of properties files and ResourceBundles for localization, Locale class for specifying locales, and MessageFormat for variable text formatting.
Appium - Reality check on the world’s leading Open Source Framework for Mobil...
Appium is clearly the world leading framework for mobile apps test automation. Adoption of Appium is in constant rise, and for the good reasons.
Yet, in many cases those who do their initial steps or even progressing with the framework realize that the world is not that simple, challenges arise, limitations are discovered and one can find himself wondering whether the right decision was taken in investing the time and money into it (yes... open source cost you money).
In this talk we will pause for a while, review why Appium is an outstanding framework, while also do a reality check of the cons and pros of Appium, helping you make the best out of it, or at least have a clear understanding of what's ahead of you.
Pender presentation 2.0
Lorin Beer's presentation from the SF PhoneGap Meetup on November 28, 2012. Pender is a cross platform library which offers hardware accelerated graphics through a Canvas API on mobile devices.
Mono for Android... for Google Devs
The document summarizes a presentation given by Craig Dunn on Mono for Android at a Google Developer Group meeting. It discusses how Mono for Android allows developers to build Android applications using C# in MonoDevelop or Visual Studio. It also covers how code can be reused across Android, iOS, and Windows platforms. The presentation included demos of building a simple Android app in C# and examples of cross-platform apps developed with Mono.
The Ring programming language version 1.5.1 book - Part 4 of 180
This document summarizes Ring, an innovative programming language designed to be simple, small, flexible and fast. Key features include a hybrid compiler and virtual machine, declarative and natural language programming, compact syntax without semicolons, first class variables, lists, objects and functions, automatic memory management, and cross-platform support. The language aims to provide high productivity for tasks like rapid application development, scripting, and building visual programming tools.
Introduction to xamarin
Xamarin enables developers to write mobile apps using C# and share code across platforms like iOS and Android. Developers can build native user interfaces and take advantage of native performance on each device, while sharing up to 90% of their code. This hybrid approach allows building apps for over 2.5 billion devices using C# and the .NET framework in Visual Studio. Key benefits include writing everything in C#, 100% API coverage on all platforms, and always being up to date with the latest APIs.
Internationalization in Angular Presentation
Internationalization, sometimes referenced as i18n, is the process of supporting multiple languages in our applications. In this session, we will demonstrate how we can enable our angular application to target any language in the world using ngx-translate.
Introduction to Xamarin Development
This document discusses cross-platform mobile app development using Xamarin. It introduces Xamarin, which allows developers to write native mobile apps in C# that can target iOS, Android, and Windows platforms, while sharing common code. The document compares different cross-platform approaches like silo, HTML5, and Xamarin. It also provides information on Xamarin licensing options for students.
Once CODE to rule them all
This document discusses using domain specific languages (DSLs) to help address challenges in developing mobile applications for multiple platforms. It introduces the Applause framework, an XText-based DSL for creating mobile apps, which uses code generation to produce applications for iOS and Android from a single codebase. An example SASSI Pocket Guide app is demonstrated to show how concepts like entities, views and navigation are mapped to the DSL and then generated to native mobile platforms.
Introduction to xamarin
Xamarin enables developers to write native mobile apps in C# that can run on iOS, Android, and Windows platforms. It allows code-sharing so the majority of the code can be shared across platforms while maintaining native user interfaces and performance. Key benefits include writing apps once in C# and deploying to over 2.5 billion devices, near 100% API coverage on all platforms, and leveraging Visual Studio and .NET frameworks for development.
Comparisons react native vs. flutter vs. ionic vs. xamarin vs. native script
When it comes to mobile app development, one can choose between fully native and cross-platform applications. Both approaches have their own unique advantages. This topic will provide you with a comparison of some of the most popular app development frameworks – 5, to be exact. These include React Native, Flutter, Xamarin, NativeScript, and Ionic.
The Ring programming language version 1.5.2 book - Part 5 of 181
This document provides an overview of the Ring programming language. It discusses the motivation for creating Ring, which was to build a new version of Programming Without Coding Technology software from scratch using a single language. Ring aims to be innovative, practical, simple, small, flexible and fast. It supports multiple programming paradigms and can be used to create various application types. The document outlines Ring's features, which include its hybrid compiler/virtual machine implementation, declarative programming support, natural language programming, portability and more. It is open source under the MIT license.
Cross platform mobile approaches
This document discusses cross-platform mobile development. It defines cross-platform development as developing applications that can run on multiple platforms simultaneously. The document then explores different cross-platform approaches like web apps, hybrid apps, interpreted apps, cross-compiled apps, and generated apps. It provides details on how each approach works and when they are involved in the development process. The document also compares the different approaches based on factors like native access, performance, cost, and tools. It concludes that cross-platform options are not fully mature but can be good choices for prototypes, existing web apps, or as a shortcut to the market.
The Ring programming language version 1.10 book - Part 6 of 212
This document provides an overview and history of the Ring programming language. It discusses the motivations for creating Ring, which was to have a dynamic, small, and productive language for building applications and development environments. Ring draws influence from languages like Lua, Python, Ruby, C, C#, and BASIC. The document outlines the language's features, which include support for declarative and natural language programming, flexibility in syntax, portability across platforms, and automatic memory management.
The Great Mobile Debate: Native vs. Hybrid App Development
It’s not easy being a mobile developer. iOS and Android dominate the market, Windows Phone is climbing into third place, and we’re not really sure if BlackBerry still matters. Do you focus on one platform or many? What size of the mobile population do you really want to reach? Each mobile platform comes with its own programming languages, SDKs, IDEs and application lifecycle & architecture. Are we really expected to learn all of this? Isn’t HTML5 supposed to be the Silver Bullet so we can finally write apps once and run them everywhere? This session will demystify all these questions, walking you through the modern mobile ecosystem, and explore your options as a developer. We’ll review the native story on each major platform, discuss the pros & cons of both mobile native and web development, cover some of the cross-platform solutions available to developers, and explore best practices and guidelines to insure a successful mobile strategy. Don’t just blindly pick a side or assume that “one size fits all”, this session covers one of the most hotly contested debates in modern IT. Come join us and be a part of the conversation.
Similar to Affordable and efficient multi platform localisation. case study (20)
[Srijan Wednesday Webinars] Building Full-Fledged Native Apps Using RubyMotion
[Srijan Wednesday Webinars] Building Full-Fledged Native Apps Using RubyMotion
Appium - Reality check on the world’s leading Open Source Framework for Mobil...
Appium - Reality check on the world’s leading Open Source Framework for Mobil...
The Ring programming language version 1.5.1 book - Part 4 of 180
The Ring programming language version 1.5.1 book - Part 4 of 180
Comparisons react native vs. flutter vs. ionic vs. xamarin vs. native script
Comparisons react native vs. flutter vs. ionic vs. xamarin vs. native script
The Ring programming language version 1.5.2 book - Part 5 of 181
The Ring programming language version 1.5.2 book - Part 5 of 181
The Ring programming language version 1.10 book - Part 6 of 212
The Ring programming language version 1.10 book - Part 6 of 212
The Great Mobile Debate: Native vs. Hybrid App Development
The Great Mobile Debate: Native vs. Hybrid App Development
Affordable and efficient multi platform localisation. case study
- 1. Affordable and efficient multi platform localization. Case study
- 2. Contens ● Internaziolization vs Localization ● Android vs Ios ● How prepare it ● Our experience
- 4. Internazilization Internationalization is the process of making your app able to adapt to different languages, regions, and cultures.
- 5. Localization Localization is the process of translating your app into multiple languages.
- 10. Strings.xml
- 11. The winner is ... ?
- 13. HOW PREPARE IT
- 14. Gold rule of Localization USE FORMATTER INSTEAD OF CONCATENATION
- 15. Usge of formatter Hello, userName! You are (n) visitor.
- 16. Usage of formatter Hello, userName! You are (n) visitor.
- 17. Usage of formatter Hello, userName! You are (n) visitor.
- 18. Usage of formatter Hello, userName! You are (n) visitor.
- 20. Quantity
- 23. Quantity in Ios
- 24. Quantity in Ios
- 26. Localization of other resources
- 27. LaMetricTime date Localization Example
- 28. LaMetricTime metrics Localization Example
- 29. LaMetricTime Localization of Backend responses
- 30. Other things to remeber 1. Localize images 2. Set correct layout
- 31. Common mistakes
- 32. Usage of string concatenation
- 34. Magic methods insted of localizing plurals
- 35. Our experience
- 36. What we need to localize ? 1. Android app 2. Ios app 3. Cloud 4. Firmware
- 38. OneSky UI
- 39. OneSky app 1. Fast translation 2. Translation is made by native speakers 3. Comfortable UI 4. Cheap price 5. Awesome quality
- 40. How making it 2x cheaper ? ● More than 95% of text and all resources in both applications was the same. ● So why we need to pay 2x price for each Localization ?
- 41. Solution ANDROID KEYS == IOS KEYS
- 42. How we make it ● IOS Localization contain only one file. ● All Storyboard & Xib texts are set from code ● All IOS keys changed to android keys
- 43. Results ● 95% of text resources was localized ● We need to localize only 2 files all the time ● Localization is 2x cheaper
- 44. How make Localization fast ● Take care about Localization from project beginig ● Use same keys for android & ios app ● Choose correct Localization Service
- 45. Thank you :)