Localize is a no-code translation solution for SaaS platforms, allowing you to easily translate your web app, dashboard, API docs, and much more. With Localize you can translate your web app and website in minutes, not months.

Localize

Hi! My name’s Amir. I’m a Web3 Community Manager and a podcast host. To improve the reach of my podcast, 2 months ago, I tried the Rask.ai platform, and have edited over 10 hours of footage since. In this review, I’ll go into the challenges Rask.ai can solve for you, its features, and the pros/cons of the platform. What Is Rask.ai, and Why Did I Buy It? Essentially, Rask.ai is a platform that uses AI for video/audio localization and repurposing. By repurposing, I mean auto reframing to vertical format, and auto-editing long videos to capture the most interesting moments. Rask.ai poses itself as a platform that has all the AI features for content makers in one place, a one-stop-shop of some sort. In one subscription, you get all the AI tools you would need to make your video content better. The main purpose that I had in mind when checking out Rask.ai was to increase the reach of my podcast on TikTok and YouTube. The podcast originally is in Kazakh, but to expand the potential audience and potential advertisers, I was looking for ways to target the English-speaking market as well. Price, Interface, and Functionality The platform is very flexible when it comes to pricing: you have 3 options to choose from, which vary by the price, the amount of minutes, and other available features. Honestly, I think the only metric you should really look at is the amount of minutes, as it will influence your work the most. I’ve picked the second plan, Creator Pro. It includes 100 minutes of edited footage per month and costs me $120. They also offer a plan for $50 and 25 minutes, as well as a corporate plan - $600 and 500 minutes. The biggest plan the platform offers is enterprise, which starts at 2000 minutes with a custom price. Note that all prices are correct if you pay annually - plans with monthly payments will be ~15% more expensive. Last month, I had 2 podcasts instead of one, and I ran out of minutes on my regular plan. However, you can always buy additional minutes at a $3 rate. Setting up the account is very easy (as it should be in 2024): you can use your Google account to log in or create the account with your email. The interface is very clean and isn’t overloaded by different buttons and links. You have FAQ and customer support at the top right corner, accessible from any page, so if you get a bit confused, there’s always that. I can’t say that I’m a tech guru of any kind, but I got used to the website in a matter of minutes. I’ve never worked with a mobile version of the site as I always store all raw footage on my Mac, but if you’re editing a small TikTok/Reels, you can easily do it from your phone. What Does Rask.ai Do, and How Do I Use It? The platform has 2 main features: localization and shorts. Let’s start with the first one, which became a selling point for me. You download a video from your device or paste a link from YouTube or Google Drive, choose the number of speakers, original language, and the language you want to translate the video to, and click “translate.” After that, the magic begins. In a matter of minutes (depending on the length of the video), you get the same video but translated to a different language. The voice-over keeps the voice’s depth, tone, and emotion, and even creates a lip sync, so the video footage is similar to the audio. How do I use that feature? Before discovering Rask.ai, in order to reach the English-speaking market, I was adding EN subtitles to all my podcasts. However, that approach was far from ideal as I was always encountering many barriers: Time-consumption. The current speech-to-text AI solutions are very far from perfect. On 100 AI-generated subtitles, I was getting ~30 errors that I needed to edit manually. Scale that to hours of footage and thousands of text, and you get yourself many hours of manual work.


Accessibility. Subtitles can’t be a permanent solution to expand your foreign audience, especially when it comes to podcasts. When was the last time you paid attention to video footage on a podcast? People listen to them while exercising, cooking, cleaning, and working. My podcast gets 40% more listeners on Spotify and Google Podcasts (which don’t have video) vs YouTube (which has video), meaning that people aren’t looking at the screen and subtitles when listening.


Retention. Even if a person bothers to actively read the subtitles, they still are getting less than people watching the original. Many intonations, jokes, or facial expressions are just not working when perceptive through text. Listeners are too busy reading to actually relax and enjoy the podcast. The Rask.ai platform solved all these problems for me. The amount of manual work I had to do had decreased to practically 0, since in 2 months of using the platform, I haven’t encountered any errors in translations. The retention improved a lot as well: YouTube has statistics that show you how many people watch your videos until the end, and this number significantly improved, since your listeners can actually LISTEN instead of reading. Another feature that I didn’t even know about when getting the subscription to Rask.ai is Shorts. Basically, it takes your hour-long footage and splits the most interesting moments into many short vertical videos. As you probably know, one of the best ways to promote your podcast in 2024 is to share these videos on TikTok, Shorts, and Reels, because these platforms have much better recommendation systems than YouTube, and putting the link to the full podcast in your bio. That’s how I personally discovered many of my favorite podcasts and began to host them myself. Before discovering that feature, I had a friend on a part-time salary doing that for me, because apart from the podcast, I also have a full-time job in Web3 that is taking a significant part of my day. Creating 15 short videos from one podcast took us about 5-6 hours of manual work since you have to fully watch the podcast, then edit all shorts separately, and add some graphics and subtitles. When I discovered a shorts feature on Rask.ai, the same amount of work took me from 5 to 10 minutes (again, depending on the length of the footage). This let me cut my editorial costs down to the sole price of my Rask.ai plan, without having to pay the salary to a whole person doing that. And you say AI won’t take our jobs :) There are a couple of smaller features that I haven’t really tested a lot until today, but I’m planning on exploring them in the future as well. For example, subtitles generation, and API for translations. The company also plans on integrating some features that I’m really excited about: AI video generation (Like MidJourney, but videos), and Zapier integration. Pros, Cons, and Who Can Use It? In conclusion, Rask.ai won’t make your video content more interesting or helpful and won’t make you a superstar overnight. However, with the right distribution strategy and exciting content, Rask.ai will significantly cut your editorial costs, saving you hundreds of dollars on people who translate and edit your content for you, as well as save you A LOT of time, letting you focus on the stuff that really matters: scripts, topics, guests, and other things that make your content better. Rask.ai is a great solution for podcast hosts like myself, social media or community managers producing content for their companies, or TikTok and Instagram influencers that focus on short video content. Pros: Clean and simple interface
Precise translations
Multiple features in one subscription Cons: Relatively high prices
Not all features are ready yet Hi! My name’s Amir. I’m a Web3 Community Manager and a podcast host. To improve the reach of my podcast, 2 months ago, I tried the Rask.ai platform, and have edited over 10 hours of footage since. In this review, I’ll go into the challenges Rask.ai can solve for you, its features, and the pros/cons of the platform. What Is Rask.ai, and Why Did I Buy It? What Is Rask.ai, and Why Did I Buy It? Essentially, Rask.ai is a platform that uses AI for video/audio localization and repurposing. By repurposing, I mean auto reframing to vertical format, and auto-editing long videos to capture the most interesting moments. Rask.ai poses itself as a platform that has all the AI features for content makers in one place, a one-stop-shop of some sort. In one subscription, you get all the AI tools you would need to make your video content better. The main purpose that I had in mind when checking out Rask.ai was to increase the reach of my podcast on TikTok and YouTube. The podcast originally is in Kazakh, but to expand the potential audience and potential advertisers, I was looking for ways to target the English-speaking market as well. Price, Interface, and Functionality Price, Interface, and Functionality The platform is very flexible when it comes to pricing: you have 3 options to choose from, which vary by the price, the amount of minutes, and other available features. Honestly, I think the only metric you should really look at is the amount of minutes, as it will influence your work the most. I’ve picked the second plan, Creator Pro. It includes 100 minutes of edited footage per month and costs me $120. They also offer a plan for $50 and 25 minutes, as well as a corporate plan - $600 and 500 minutes. The biggest plan the platform offers is enterprise, which starts at 2000 minutes with a custom price. Note that all prices are correct if you pay annually - plans with monthly payments will be ~15% more expensive. Last month, I had 2 podcasts instead of one, and I ran out of minutes on my regular plan. However, you can always buy additional minutes at a $3 rate. Setting up the account is very easy (as it should be in 2024): you can use your Google account to log in or create the account with your email. The interface is very clean and isn’t overloaded by different buttons and links. You have FAQ and customer support at the top right corner, accessible from any page, so if you get a bit confused, there’s always that. I can’t say that I’m a tech guru of any kind, but I got used to the website in a matter of minutes. I’ve never worked with a mobile version of the site as I always store all raw footage on my Mac, but if you’re editing a small TikTok/Reels, you can easily do it from your phone. What Does Rask.ai Do, and How Do I Use It? What Does Rask.ai Do, and How Do I Use It? The platform has 2 main features: localization and shorts. Let’s start with the first one, which became a selling point for me. You download a video from your device or paste a link from YouTube or Google Drive, choose the number of speakers, original language, and the language you want to translate the video to, and click “translate.” After that, the magic begins. In a matter of minutes (depending on the length of the video), you get the same video but translated to a different language. The voice-over keeps the voice’s depth, tone, and emotion, and even creates a lip sync, so the video footage is similar to the audio. How do I use that feature? Before discovering Rask.ai, in order to reach the English-speaking market, I was adding EN subtitles to all my podcasts. However, that approach was far from ideal as I was always encountering many barriers: Time-consumption. The current speech-to-text AI solutions are very far from perfect. On 100 AI-generated subtitles, I was getting ~30 errors that I needed to edit manually. Scale that to hours of footage and thousands of text, and you get yourself many hours of manual work. Accessibility. Subtitles can’t be a permanent solution to expand your foreign audience, especially when it comes to podcasts. When was the last time you paid attention to video footage on a podcast? People listen to them while exercising, cooking, cleaning, and working. My podcast gets 40% more listeners on Spotify and Google Podcasts (which don’t have video) vs YouTube (which has video), meaning that people aren’t looking at the screen and subtitles when listening. Retention. Even if a person bothers to actively read the subtitles, they still are getting less than people watching the original. Many intonations, jokes, or facial expressions are just not working when perceptive through text. Listeners are too busy reading to actually relax and enjoy the podcast. Time-consumption. The current speech-to-text AI solutions are very far from perfect. On 100 AI-generated subtitles, I was getting ~30 errors that I needed to edit manually. Scale that to hours of footage and thousands of text, and you get yourself many hours of manual work. Time-consumption. The current speech-to-text AI solutions are very far from perfect. On 100 AI-generated subtitles, I was getting ~30 errors that I needed to edit manually. Scale that to hours of footage and thousands of text, and you get yourself many hours of manual work. Accessibility. Subtitles can’t be a permanent solution to expand your foreign audience, especially when it comes to podcasts. When was the last time you paid attention to video footage on a podcast? People listen to them while exercising, cooking, cleaning, and working. My podcast gets 40% more listeners on Spotify and Google Podcasts (which don’t have video) vs YouTube (which has video), meaning that people aren’t looking at the screen and subtitles when listening. Accessibility. Subtitles can’t be a permanent solution to expand your foreign audience, especially when it comes to podcasts. When was the last time you paid attention to video footage on a podcast? People listen to them while exercising, cooking, cleaning, and working. My podcast gets 40% more listeners on Spotify and Google Podcasts (which don’t have video) vs YouTube (which has video), meaning that people aren’t looking at the screen and subtitles when listening. Retention. Even if a person bothers to actively read the subtitles, they still are getting less than people watching the original. Many intonations, jokes, or facial expressions are just not working when perceptive through text. Listeners are too busy reading to actually relax and enjoy the podcast. Retention. Even if a person bothers to actively read the subtitles, they still are getting less than people watching the original. Many intonations, jokes, or facial expressions are just not working when perceptive through text. Listeners are too busy reading to actually relax and enjoy the podcast. The Rask.ai platform solved all these problems for me. The amount of manual work I had to do had decreased to practically 0, since in 2 months of using the platform, I haven’t encountered any errors in translations. The retention improved a lot as well: YouTube has statistics that show you how many people watch your videos until the end, and this number significantly improved, since your listeners can actually LISTEN instead of reading. Another feature that I didn’t even know about when getting the subscription to Rask.ai is Shorts. Basically, it takes your hour-long footage and splits the most interesting moments into many short vertical videos. As you probably know, one of the best ways to promote your podcast in 2024 is to share these videos on TikTok, Shorts, and Reels, because these platforms have much better recommendation systems than YouTube, and putting the link to the full podcast in your bio. That’s how I personally discovered many of my favorite podcasts and began to host them myself. Before discovering that feature, I had a friend on a part-time salary doing that for me, because apart from the podcast, I also have a full-time job in Web3 that is taking a significant part of my day. Creating 15 short videos from one podcast took us about 5-6 hours of manual work since you have to fully watch the podcast, then edit all shorts separately, and add some graphics and subtitles. When I discovered a shorts feature on Rask.ai, the same amount of work took me from 5 to 10 minutes (again, depending on the length of the footage). This let me cut my editorial costs down to the sole price of my Rask.ai plan, without having to pay the salary to a whole person doing that. And you say AI won’t take our jobs :) There are a couple of smaller features that I haven’t really tested a lot until today, but I’m planning on exploring them in the future as well. For example, subtitles generation, and API for translations. The company also plans on integrating some features that I’m really excited about: AI video generation (Like MidJourney, but videos), and Zapier integration. Pros, Cons, and Who Can Use It? Pros, Cons, and Who Can Use It? In conclusion, Rask.ai won’t make your video content more interesting or helpful and won’t make you a superstar overnight. However, with the right distribution strategy and exciting content, Rask.ai will significantly cut your editorial costs, saving you hundreds of dollars on people who translate and edit your content for you, as well as save you A LOT of time, letting you focus on the stuff that really matters: scripts, topics, guests, and other things that make your content better. Rask.ai is a great solution for podcast hosts like myself, social media or community managers producing content for their companies, or TikTok and Instagram influencers that focus on short video content. Pros: Pros: Clean and simple interface Precise translations Multiple features in one subscription Clean and simple interface Precise translations Multiple features in one subscription Cons: Cons: Relatively high prices Not all features are ready yet Relatively high prices Not all features are ready yet

How to Localize Your Shorts in 3 Clicks

Most mobile apps and games, big and small, support multiple languages, as it is simply counter-productive to spend a lot of time and resources on app development and then reduce the audience to speakers of just one language. Usually, this one language is English, but despite its global presence, experience has shown that releasing your iOS app in just English can significantly cut into your potential downloads and, consequently, revenue. Alconost clients’ experience shows that audience volume can after localizing their app into the most-used languages. grow 10-fold Supporting multiple languages is essential for the organic growth of downloads and conversions into paying users. For example, check out how the number of organic installs for Narcade’s mobile apps grew in Korea after translating their games into Korean. More and more iOS developers are realizing that covering a wide range of languages is one of the keys to growth in terms of both downloads and revenue. The team of photo editing app RetouchMe, for example, started off with just a few languages, but after realizing how many more international users they could reach with localization, they expanded their range of languages to 35, and that localization into all 35 languages . paid off The chart below shows how their App Store ranking changed after localizing the app and its App Store page (for Brazil, Italy, and Turkey). The team generously shared more screenshots with stats in . this case study How do you choose for localizing your game? See what non-English speaking markets you’re getting downloads from. There is a good chance that localizing your app properly will boost your downloads in those markets. the right languages Some companies prefer to start with (translating the app store description, the title and subtitle, and the copy of the screenshot) to see how localization will influence conversions on the App Store. After seeing the results, they will then decide to localize the whole app. ASO localization Informed Decision for iOS Localization: The Pros and Cons of the Popular Options How can your team approach iOS localization? First off, make sure you’ve prepared your game for localization. In , we’ll walk you through the key preparation steps. this guide But how do you tackle localization as a process? Let’s take a look at the available options and discuss their advantages and drawbacks. Machine Translation Though we generally don’t recommend machine translation for customer-facing content, sometimes companies turn to this solution to cut down on costs. It may work for very simple casual games when the key purpose is to make the UI understandable for gamers. We should mention that just using the free Google Translate might not do the trick, and is likely to set you up for translation failures. The best practice is to use machine translation APIs, such as Google API and DeepL API. But you can expect good enough quality only if you have a large translation memory for your game content to train the machine translation engine properly. Another way to use machine translation and get an adequate translation is , where professional native-speaking translators edit your machine-translated content. However, the chances are that translators will deem the quality of this translation too low, and will charge their full rate. PEMT: Post-editing machine translation Here is a vivid example from one of our clients, the gaming company Full HP, who managed to . The client approached Alconost with English-to-Korean and English-to-Japanese translations. These game texts were machine-translated, after which the Full HP team ordered from Alconost for this content. combine machine and professional translation for their games post-editing The content contained dialogues, and unfortunately, machine translation failed to adapt the dialogues into Korean. As a result of the poor quality, the entire translation had to be done from scratch, and the client had to order the English-to-Korean translation with the standard translation workflow. The Full HP team went with this suggestion and received high-quality localization and content gamers. As a result, the team was able to strike a balance between using third-party machine translation for more generic and simple content while localizing more context-heavy texts with Nitro, Alconost’s human translation platform. This approach the in-app conversion rate by 25%. helped increase Community Translation and Freelance Translators This is another tempting option for saving money on localization. If you can boast a large and active community, you can go for this option. Your gamers know your game inside and out, so there shouldn’t be too many contextual mistakes. The main drawbacks of this approach are translation inconsistency and the amount of time it takes, as gaming enthusiasts are not professionals and are working on the translation in their free time. On the one hand, freelance translators are a better option; they are usually professional translators, and you can expect them to stick to the deadlines. However, we’ve noticed that many of our clients turned to Alconost because they found managing freelance translators too cumbersome and time-consuming. Here is what the has to say about it: Narcade team “Before Alconost and Nitro, we worked with freelance translators via a crowdsourcing platform. Naturally, the process took more time and was more complex (and small wonder, what with contacting each translator separately for each language pair!). In addition, we weren’t sure the translations were accurate. With Nitro, it’s an easy matter for us to send the text for translation into multiple languages simultaneously: we just copy the text, specify the languages needed, and receive our translated texts within 24 hours!” Human Translation Platform Nitro: The Best of Both Worlds Alconost has developed its own translation platform, Nitro, which combines professional native-speaking translators and the convenience of a self-service platform saving time for the client. The good news is that translations through Nitro are quite affordable. is a human translation platform that supports over 70 translation languages and boasts a fast turnaround. All translations are carried out by professional translators, who have been working with Alconost long-term. Nitro The self-service mode allows clients to place translation orders independently, without reaching out to Alconost’s localization managers. It is also a convenient way to translate app store descriptions, text on screenshots, and frequent updates, as there is no minimum order. Here is why Nitro can be a good fit for localizing your iOS game: Easy order placement. When you add content for translation and tick off the required languages, you’ll get an automatically-calculated quote right away; Support for .strings. Download your .strings file and receive the translation in the same format; Context information. Attach screenshots, choose the tone of voice, and leave notes for translators to provide context. The context within the .strings file will also be visible to translators; API. You can use to cut down on the work needed from your side, like manually uploading and downloading the localized content, and enjoy quality localization without extra effort; Nitro API A translation memory and discounts for repetitions. Nitro stores all your previous translations in the translation memory, allowing them to be reused when an identical segment pops up. So, for a 100% phrase match, we will discount the translation of the repeated phrase by 70%; Character limit restriction . App Store copy or UI buttons usually have a character limit restriction, and on Nitro, you can set this restriction and ensure the translations fit the allocated space. (optional) what the Nitro platform looks like! Try adding your content, play around with choosing languages, and you’ll get an instant quote—all without even creating an account. Check out If you have questions or any issues, you get in touch with Nitro’s support team in the live chat and get a reply within 10-15 minutes. Just like Nitro’s turnaround time, it is fast. For questions to the translators, you can send your order for revision on Nitro and add your question. You’ll receive a reply directly from the translator. This human translation platform is especially convenient for translating smaller games, updates, and marketing content. Large projects requiring , Mobile SDK integration, support for a wide range of file formats, and other adjustments are better handled on cloud-based . Such projects are managed by a PM who helps set up a seamless localization process. continuous localization localization platforms Summary iOS localization has become a must in the highly competitive app market. Experienced publishers and app development companies recommend localizing both your app store page (including screenshots localization) and the app itself and making sure the translation considers all contexts. While you do have a choice between machine and human translation, it’s best to go for the latter to avoid translation failures. For each mobile app or game, you’ll need to strike a balance between the risks and costs. It’s important to point out that if you’ve gone with a low-quality, high-risk solution, your conclusions about inefficient localization results in a certain language might be incorrect, simply because you cannot be sure what put off your users; it could very well be the poor quality of localization. Even one sloppily translated button may result in poor conversion rates and hurt monetization. So it’s essential to choose a quality solution. If your iOS app is smaller and does not have a lot of content for translation, it is best to go with the easier and more affordable option of the self-serve human translation platform. This will allow you to skip the step of sending the files to a localization agency just to get a quote and further back and forth. This option is also the best fit for fast and professional translations for app store descriptions, screenshots copy, and in-app updates. For larger projects, however, you may prefer more advanced localization platforms as they have more customization options. Do you need to localize your mobile game?

How to Localize Your iOS App and Reach a Global Audience?

Localize your iOS applications with Transifex Native: A How-To Guide

How We Localized Our Website in 9 Languages in Under a Week — And So Can You

This example project has everything you need to localize your native iOS and macOS applications on our platform, using a fully automated approach. Smartcat continuous localization What we offer here is a pre-configured Docker container with our command-line localization automation tool, , which will pull the changes from your code repository, parse the source and files, send translation data over to Smartcat, get translations back, integrate them into its local database, generate localized files and push them back to your repo, all in a single sweep. Serge (String Extraction and Resource Generation Engine) .strings .plist See >>> bootstrap project at github This approach to localization: Doesn't require writing custom low-level integration code: you write declarative configuration files instead Doesn't require you to change your CI/CD build process: translations are integrated statically into your source code repository Is secure: you don't give Smartcat direct access to your source code repositories, and you control all the synchronization Is vendor lock-in free: you own your translation data, and can generate localized resource files completely offline Is flexible: you can manually run it on your computer, or run it on a schedule on a dedicated host Is powerful: you can implement localization workflows that otherwise would require many months of development (see below). Features With our continuous localization solution, you have an unprecedented flexibility and power. Some ideas that might inspire you are: Automatic discovery and localization of multiple product branches Ability to prohibit localized file updates unless they are 100% translated (handy for marketing materials!) Ability to specify target languages right in each file, to enable automated self-service scenarios Pseudo-localization for easier internationalization (i18n) QA Conditional exclusion of certain strings by mask Ability to auto-generate comments and preview links for each string Ability to group multiple repositories and different file types under a same logical project Ability to preprocess source files for greater flexibility Ability to post-process localized files so that the final result is CI/CD-ready Ability to email developers if source files are broken ... and much more! Installation 1. for your Windows, Mac, or Linux. Install Docker 2. Run this command to install Serge for the first time, or to update it to a latest version: $ docker pull smartcatcom/serge 3. Clone this repository into any directory: $ git clone https: //github.com/smartcatai/smartcat-serge-bootstrap-ios-native.git 4. Create an account at Smartcat. 5. Create a new project in Smartcat to synchronize your data with, with as a source and and as target languages (don't worry, you will be able to change the settings later). English German Russian Getting Started Running Serge in interactive mode In the root directory of this repo we have provided you a convenience script to run a Serge shell, from which you will have access to command. Run it as follows (both under Windows, Mac or Linux): serge $ ./serge-shell When you enter your shell, the root directory of your bootstrap project will be mounted as and you will see the following prompt: /data [Serge Shell] /data $ Here and below, it is assumed that you're running the commands inside this shell. At the same time, you can continue editing the configuration files or browse the directory outside of the shell in Explorer, Finder, or any other favorite file management tool and code editor. Note: Now you that you are inside this interactive shell, you can run Serge (the command below will just show some short usage synopsis and a list of available commands): $ serge To exit the shell later, use the command: exit $ exit Getting around This repository contains a sample project, . First things to do are: ios-native See the configuration file: configs/ios-native.serge Look at the contents of the source project folder: vcs/ios-native This sample project is set up to have (English) as a source language and (German) and (Russian) as target languages, and will process all keys in the resource file in directory. en de ru strings.xml vcs/ios-native/en.lproj Initial run Go to the directory and run the localization step: configs $ cd configs
$ serge localize This will create localized files under and directories. These files will have English content, since translations have not been provided just yet. vcs/ios-native/de.lproj vcs/ios-native/ru.lproj The same localization step will generate translation files under and directories. You can examine the generated files and also see their initial state with no translations. ts/ios-native/de ts/ios-native/ru .po Doing translations locally Edit e.g. file and provide a translation for a single string (for testing purposes, any random "translation" will work). ts/ios-native/de/Localizable.strings.po Run once again from the directory. If you now open the localized resource file, e.g. , you will see that your translation has been integrated into this resource file. serge localize configs vcs/ios-native/de.lproj/Localizable.strings Connecting with Smartcat Create a new project in Smartcat with as a source language and and as target ones. Languages must be registered on the project before you can upload files targeting those languages. You can later change the list of target languages at any time. English German Russian Edit the file and fill out your account parameters and credentials under config section: , , and . Instructions next to each parameter will help you understand where to get the values from. Once defined, these settings will be shared across your future localization projects. configs/common.serge.inc common-settings → ts base_url account_id token Edit the file and specify the , following the instructions in the configuration file. configs/ios-native.serge project_id Now you can push your translation files to Smartcat: $ serge push-ts Go to Smartcat, open the test project you created, and there you will see your , , , and files available for translation: two files are for German, and another two are for Russian. Localizable.strings_de strings.plist_de Localizable.strings_ru strings.plist_ru Open e.g. e and edit the translation for the string that you translated previously. Localizable.strings_d Now you can pull translations from Smartcat and run a localization cycle at once: $ serge pull-ts localize If you now open the localized resource file, , you will see that your translation has been integrated into this resource file. vcs/ios-native/de.lproj/Localizable.strings Running the localization continuously This project has two convenience scripts, and that you can use as a starting point for your continuous localization process. sync-once.sh sync-loop.sh Run to run the sync/localization cycle just once. ./sync-once.sh Run to run the sync/localization cycle every 5 minutes. You can edit the file and put any delay you want. ./sync-loop.sh While the localization is running in background (eventually you will want to run it on a dedicated server), you can modify your example project (add, change or delete keys in your source XML file) and provide translations on Smartcat side at the same time, and Serge will merge in all these changes, gathering the new translations, updating the localized resources, and pushing new strings for translation. Adding VCS synchronization The last missing step is to make Serge not only generate the localized files locally, but also pull the sources from your actual source code repository, and push localized files back to the remote repo. Since Git is the most popular version control system, this sample project includes a stub for connecting to a Git repo. Edit the file so that parameter points to the actual remote repository URL. Now initialize the data from the remote repo (this will remove the previous contents of folder with the contents of your repository): configs/ios-native.serge → sync → vcs → data → remote_path vcs/ios-native $ serge pull --initialize ios-native.serge The parameter in this command is needed only once, when you want to delete and re-populate the contents of the project folder. --initialize Now your project has a different directory structure, and maybe different files (not JSON), so you need to edit your file accordingly (see , , parameters, and the section). configs/ios-native.serge → jobs → (first job section) → source_dir source_match output_file_path parser At this point we recommend you to spend some time reading the for the list of available parsers and their parameters, and the . Serge documentation configuration file syntax and reference Once you have your job parameters tweaked, it's time to test this by running a localization cycle once again, and also cleaning up the outdated translation files: $ serge localize
$ serge clean-ts If you see that a set of localized files was properly created in your folder, and that translation files in folder also look good, you can push the localized files back to the remote repository: vcs/ios-native ts/ios-native $ serge push The last and final step is to enable the full synchronization cycle. Edit the script by disabling the line and enabling the line. The latter command is equivalent to . In human language, this means that running will do everything a continuous localization is expected to do: pull the new contents from both your Git server and Smartcat, update localized resources and translation files, and push changes back to Git and Smartcat, respectively. sync-once.sh serge pull-ts localize push-ts serge sync serge pull pull-ts localize push-ts push serge sync Finally, run: ./sync-loop.sh Congratulations! You now live in the world of smooth continuous localization . (press Ctrl+C anytime to get back to reality) Running Serge in a non-interactive mode When you don't need an interactive shell (especially when you're running Serge on a dedicated server), you can use a provided wrapper, as follows: run-in-docker $ ./run- -docker serge localize configs/ios-native.serge in or: $ ./run- -docker ./sync-loop.sh in Adding new projects In the paradigm of continuous localization, your Smartcat projects will be permanent; content in these projects will be constantly updated, reflecting the changes in your repositories and external content sources. You can create one project for your iOS application, another one for Android, for your website, documentation, and so on. To set up a new project (besides creating one in Smartcat), you will need to make a copy of to (of course, file and project names are up to you), and edit a new configuration file accordingly. configs/ios-native.serge configs/project-b.serge Getting professional support At Smartcat, we strive to build delightful localization processes that work seamlessly and don't slow you down. We offer managed solutions and localization engineering services , so you don't have to figure this out all by yourself! as a part of the subscription Also published at: https://github.com/smartcatai/smartcat-serge-bootstrap-ios-native

How to Localize your Native iOS and macOS Applications on Smartcat

This example project has everything you need to localize your native Android application on platform, using a fully automated approach. Smartcat continuous localization See >>> bootstrap project at github What we offer here is a pre-configured Docker container with our command-line localization automation tool, , which will pull the changes from your code repository, parse the source file, send translation data over to Smartcat, get translations back, integrate them into its local database, generate localized files and push them back to your repo, all in a single sweep. Serge (String Extraction and Resource Generation Engine) strings.xml This approach to localization: Doesn't require writing custom low-level integration code: you write declarative configuration files instead Doesn't require you to change your CI/CD build process: translations are integrated statically into your source code repository Is secure: you don't give Smartcat direct access to your source code repositories, and you control all the synchronization Is vendor lock-in free: you own your translation data, and can generate localized resource files completely offline Is flexible: you can manually run it on your computer, or run it on a schedule on a dedicated host Is powerful: you can implement localization workflows that otherwise would require many months of development (see below). Features With our continuous localization solution, you have an unprecedented flexibility and power. Some ideas that might inspire you are: Automatic discovery and localization of multiple product branches Ability to prohibit localized file updates unless they are 100% translated (handy for marketing materials!) Ability to specify target languages right in each file, to enable automated self-service scenarios Pseudo-localization for easier internationalization (i18n) QA Conditional exclusion of certain strings by mask Ability to auto-generate comments and preview links for each string Ability to group multiple repositories and different file types under a same logical project Ability to preprocess source files for greater flexibility Ability to post-process localized files so that the final result is CI/CD-ready Ability to email developers if source files are broken ... and much more! Installation 1. for your Windows, Mac, or Linux. Install Docker 2. Run this command to install Serge for the first time, or to update it to a latest version: $ docker pull smartcatcom/serge 3. Clone this repository into any directory: $ git clone https: //github.com/smartcatai/smartcat-serge-bootstrap-android-native.git 4. Create an account at Smartcat. 5. Create a new project in Smartcat to synchronize your data with, with as a source and and as target languages (don't worry, you will be able to change the settings later). English German Russian Getting Started Running Serge in interactive mode In the root directory of this repo we have provided you a convenience script to run a Serge shell, from which you will have access to command. Run it as follows (both under Windows, Mac or Linux): serge $ ./serge-shell When you enter your shell, the root directory of your bootstrap project will be mounted as / and you will see the following prompt: data [Serge Shell] /data $ Here and below, it is assumed that you're running the commands inside this shell. At the same time, you can continue editing the configuration files or browse the directory outside of the shell in Explorer, Finder, or any other favorite file management tool and code editor. Note: Now you that you are inside this interactive shell, you can run Serge (the command below will just show some short usage synopsis and a list of available commands): $ serge To exit the shell later, use the command: exit $ exit Getting around This repository contains a sample project, . First things to do are: android-native See the configuration file: configs/android-native.serge Look at the contents of the source project folder: vcs/android-native This sample project is set up to have (English) as a source language and (German) and (Russian) as target languages, and will process all keys in the resource file in directory. en de ru strings.xml vcs/android-native/src/main/res/values Initial run Go to the directory and run the localization step: configs $ cd configs
$ serge localize This will create localized files under and directories. These files will have English content, since translations have not been provided just yet. vcs/android-native/de vcs/android-native/ru The same localization step will generate translation files under and directories. You can examine the generated files and also see their initial state with no translations. ts/android-native/de ts/android-native/ru .po Doing translations locally Edit e.g. file and provide a translation for a single string (for testing purposes, any random "translation" will work). ts/android-native/de/strings.xml.po Run once again from the directory. If you now open the localized resource file, e.g. , you will see that your translation has been integrated into the XML file. serge localize configs vcs/android-native/src/main/res/values-de/strings.xml Connecting with Smartcat Create a new project in Smartcat with as a source language and and as target ones. Languages must be registered on the project before you can upload files targeting those languages. You can later change the list of target languages at any time. English German Russian Edit the file and fill out your account parameters and credentials under config section: , , and . Instructions next to each parameter will help you understand where to get the values from. Once defined, these settings will be shared across your future localization projects. configs/common.serge.inc common-settings → ts base_url account_id token Edit the file and specify the , following the instructions in the configuration file. configs/android-native.serge project_id Now you can push your translation files to Smartcat: $ serge push-ts Go to Smartcat, open the test project you created, and there you will see your and files available for translation, one for German, and another one for Russian. strings.xml_de strings.xml_ru Open e.g. and edit the translation for the string that you translated previously. strings.xml_de Now you can pull translations from Smartcat and run a localization cycle at once: $ serge pull-ts localize If you now open the localized resource file, , you will see that the new translation has been integrated into the XML file. vcs/android-native/src/main/res/values-de/strings.xml Running the localization continuously This project has two convenience scripts, and that you can use as a starting point for your continuous localization process. sync-once.sh sync-loop.sh Run to run the sync/localization cycle just once. ./sync-once.sh Run to run the sync/localization cycle every 5 minutes. You can edit the file and put any delay you want. ./sync-loop.sh While the localization is running in background (eventually you will want to run it on a dedicated server), you can modify your example project (add, change or delete keys in your source XML file) and provide translations on Smartcat side at the same time, and Serge will merge in all these changes, gathering the new translations, updating the localized resources, and pushing new strings for translation. Adding VCS synchronization The last missing step is to make Serge not only generate the localized files locally, but also pull the sources from your actual source code repository, and push localized files back to the remote repo. Since Git is the most popular version control system, this sample project includes a stub for connecting to a Git repo. Edit the file so that parameter points to the actual remote repository URL. Now initialize the data from the remote repo (this will remove the previous contents of folder with the contents of your repository): configs/android-native.serge → sync → vcs → data → remote_path vcs/android-native $ serge pull --initialize android-native.serge The parameter in this command is needed only once, when you want to delete and re-populate the contents of the project folder. --initialize Now your project has a different directory structure, and maybe different files (not JSON), so you need to edit your file accordingly (see , , parameters, and the section). At this point we recommend you to spend some time reading the for the list of available parsers and their parameters, and the . configs/android-native.serge → jobs → (first job section) → source_dir source_match output_file_path parser Serge documentation configuration file syntax and reference Once you have your job parameters tweaked, it's time to test this by running a localization cycle once again, and also cleaning up the outdated translation files: $ serge localize
$ serge clean-ts If you see that a set of localized files was properly created in your folder, and that translation files in folder also look good, you can push the localized files back to the remote repository: vcs/android-native ts/android-native $ serge push The last and final step is to enable the full synchronization cycle. Edit the script by disabling the line and enabling the line. The latter command is equivalent to . In human language, this means that running will do everything a continuous localization is expected to do: pull the new contents from both your Git server and Smartcat, update localized resources and translation files, and push changes back to Git and Smartcat, respectively. sync-once.sh serge pull-ts localize push-ts serge sync serge pull pull-ts localize push-ts push serge sync Finally, run: ./sync-loop.sh Congratulations! You now live in the world of smooth continuous localization . (press Ctrl+C anytime to get back to reality) Running Serge in a non-interactive mode When you don't need an interactive shell (especially when you're running Serge on a dedicated server), you can use a provided wrapper, as follows: run-in-docker $ ./run- -docker serge localize configs/android-native.serge in or: $ ./run- -docker ./sync-loop.sh in Adding new projects In the paradigm of continuous localization, your Smartcat projects will be permanent; content in these projects will be constantly updated, reflecting the changes in your repositories and external content sources. You can create one project for your iOS application, another one for Android, for your website, documentation, and so on. To set up a new project (besides creating one in Smartcat), you will need to make a copy of to (of course, file and project names are up to you), and edit a new configuration file accordingly. configs/android-native.serge configs/project-b.serge Getting professional support At Smartcat, we strive to build delightful localization processes that work seamlessly and don't slow you down. We offer managed solutions and localization engineering services , so you don't have to figure this out all by yourself! as a part of the subscription Previously published at https://github.com/smartcatai/smartcat-serge-bootstrap-android-native

How To Localize Your Android App: A Step by Step Guide

At Transifex, we have been using for some time now to localize our React applications and we would like to showcase how easily you could do it in your application too. Transifex Native Why should you care about Transifex Native? Because Transifex Native is a redesign of the localization stack. Some of the traits of this new approach include: A unified localization syntax across all your projects. Ability to easily push content from your development or production environment. Transifex Native uses Over The Air (OTA) content delivery which means no need for files or back and forth between engineering and localization departments. It just works! But let's just go ahead and jump into the code and see what we can accomplish with a few lines of code and some terminal commands. Installing Dependencies We are going to showcase a simple React app with the help of the tool but the process is the same with any kind of React application. Our simple guide will start with a few commands to install all the required dependencies. create-react-app @ @ @ npx create-react-app txnative-demo cd txnative-demo npm install --save transifex/ native transifex/ react transifex/ cli npm start Next, we need to make sure we have the and environment variables. They are linked to the Transifex resource. The TOKEN is considered a public key that can read from a Transifex resource and the SECRET will be used later in our tutorial in order to push strings for translation to a Transifex resource. REACT_APP_TRANSIFEX_SECRET REACT_APP_TRANSIFEX_TOKEN The prefix is there so that the React application can in client code. REACT_APP_ resolve them Adding the Code Now that we've installed everything we need, we can open and replace its contents with the following code: App.js React ; { tx } ; { T } ;

tx.init({ : process.env.REACT_APP_TRANSIFEX_TOKEN, : }); { ( <p><T _str="hello world" /></p>
    </>
  );
}

export default App; import from 'react' import from '@transifex/native' import from '@transifex/react' token sourceLocale 'en' ( ) function App return <> Nothing fancy here right? We import our libraries, initialise Transifex Native with a token, and the project's source language. The most interesting thing here is the component. This is what marks a string that is translatable. We add our string to the attribute and when we push in a later stage this will be available in Transifex as a translatable string. <T> _str Here’s the result of what we built: Let’s also add a simple language picker with this code: React ; { tx } ; { T } ;
 
 tx.init({ : process.env.REACT_APP_TRANSIFEX_TOKEN, : }); { ( <p><T _str="hello world" /></p>
+      <button onClick={() => tx.setCurrentLocale('en')}>English</button>
+      <button onClick={() => tx.setCurrentLocale('el')}>Greek</button>
     </>
   );
 } import from 'react' import from '@transifex/native' import from '@transifex/react' token sourceLocale 'en' ( ) function App return <> We added two buttons that set the current language: Pushing Strings What we’ve done up until now is just hack our way through the code. We’ve marked our strings for translation with the component and we added two buttons to change languages, but as of now, this does nothing yet. The current state in Transifex Platform for our project is the following: We have one language: <T> And one resource with no strings inside: The next step is to push our translatable content to Transifex. This could be achieved with one command in our terminal: npx txjs-cli push \
    - - - src -token=$REACT_APP_TRANSIFEX_TOKEN \ -secret=$REACT_APP_TRANSIFEX_SECRET \ -verbose \ After we run this command we get an informative report about the strings that were parsed and pushed to Transifex: Parsing all files to detect translatable content...
⸨████████████████████████████████████████⸩ / /src/setupTests.js
✓ Processed file(s) and found translatable phrase.
✓ Content detected file(s).
/src/App.js
  └─ adb6d4ba2eded700fd14e66100fcf268: hello world
    └─ occurrences: [ ]
Uploading content to Transifex... Success
✓ Successfully pushed strings to Transifex.
Created strings: Updated strings: Skipped strings: Deleted strings: Failed strings: Errors: 5 5 5 1 in 1 "/src/App.js" 1 0 0 0 0 0 If we refresh the editor page we will see that we have one string available for the translation! Let’s translate this string: If we refresh our application and click on the “Greek” button we should see content translated: Toggling between languages we see that the translations are loaded without the need for an application reload! Taking It Up a Notch Our current language picker is hardcoded, so each time we add a new language we have to manually add a new button to our application. That’s boring. Let’s automate it! React ; { tx } ;
- { T } ;
+ { T, useLanguages } ;
 
 tx.init({ : process.env.REACT_APP_TRANSIFEX_TOKEN, : }); {
+ languages = useLanguages(); ( <p><T _str="hello world" /></p>
       <button onClick={() => tx.setCurrentLocale('en')}>English</button>
-      <button onClick={() => tx.setCurrentLocale('el')}>Greek</button>
+      {languages.map(({ code, name }) => (
+        <button key={code} onClick={() => tx.setCurrentLocale(code)}>
+          {name}
+        </button>
+      ))}
     </>
   );
 }
 
 export default App; import from 'react' import from '@transifex/native' import from '@transifex/react' import from '@transifex/react' token sourceLocale 'en' ( ) function App const return <> Simple changes again. We get the available languages from Transifex and we loop through these languages to create our switcher dynamically. Keep in mind that this is the last time we will change the code of our application! Let’s try and add a new language to Transifex and see what happens to our React application: And translate our new string to French: Let’s see what changed if we refresh our application. Voila! We got the new language without changing our code and the translation is available. Wrapping Up We’ve only touched the surface of Transifex Native but we managed to have a lot of progress in three simple steps: Mark our strings for translation through our code. Run a command to send these strings to Transifex. Translate. Not bad for ten minutes of work! If you want to try it yourself and see all the benefits of Transifex Native, you can express your interest here https://www.transifex.com/native/ And did we also mention that all this code is ? You can check out the code and of course, contribute to open-source https://github.com/transifex/transifex-javascript/ Thanks for reading and we hope we could save you some time during your next localization project! ( ) Co-authored by Thanos Kolovos and Konstantinos Bairaktaris

How To Localize A React Application Using Transifex Native

In 2017 I launched a College and University themed version of the game . College Cards, as I dubbed it, was my first ever ‘official business’, and as a 22 year old recent college grad, I was pretty excited when I sold $13,000 of the game to University of Wisconsin students just 45 days after launch. Cards Against Humanity How did I do it? Easy. I growth-hacked the College Cards Instagram page with fake followers, fake engagement, and fake everything to make it look like the game was . all the rage This way when I drove real traffic and real people to the Instagram account, it looked like College Cards was simply something you to own. had It worked well. Honestly, too well. The game went so viral that the intellectual property law firm representing the University demanded that I shut the whole thing down and threatened me with a trademark infringement lawsuit if I didn’t comply. Checkout written by the school newspaper at the time. this article Looking back, this was one of the best things to ever happen to me. It’s the reason I wound up pursuing the entrepreneurial path and why I was able to start a new company which has become 10X more valuable than College Cards ever could have been. But more on that later… Allow me to explain exactly how I growth-hacked Instagram to drive hundreds of product sales and thousands of dollars of revenues in a short period of time College Cards Instagram Follower Count = 0 The goal was fairly straightforward. Prior to launch, I wanted to create an engaging and seemingly popular Instagram page for College Cards that would showcase the game. This way, once I started driving traffic and real people to the Instagram page, they would be much more inclined to check it out, interact with a post, and perhaps even buy the game. I started out by buying 500 fake followers for the Instagram account. Perception is reality, and my plan was to make the account appear as if it was all the rage before the game was even launched. To buy the followers, I simply typed “buy Instagram followers” on Google, and went with a company that was using Google Adwords to bid on that search term. It might have cost me $20 back then to purchase 500 followers. I put in my credit card, added the , and voila! 500-ish followers followed the account by the next day. @College_Cards Instagram handle College Cards Instagram Follower Count = 500 Next, I needed a solid gallery of photos and content live on the Instagram page before I started driving traffic to it. This way once people landed on the account, they had content to peruse and tag/share with their friends. I took pictures of the game content with my iPhone. I intentionally made the combinations that I posted on Instagram as outrageous as possible. I knew that the more raunchy and ridiculous I could make it, the more buzz and word of mouth the Instagram page would generate. Fake Engagement 101 It wasn’t enough to just have fake followers. To make the account look like it was thriving and active, I also needed some of that Grade A fake engagement. I needed people liking and commenting on the game photos to create the illusion that the game was popular, hilarious, and fun. In the fake world of Instagram, manufacturing fony engagement isn’t hard to do. It’s just time consuming. Every time I’d post a new photo, I’d head over to Kylie Jenner’s Instagram account, open one of her recent photos, and comment something like: ‘LB’, ‘Lbbbbb’, or ‘LB LB :)’. You see, Instagram is a huge cesspool of fakers. ‘Engagement’ is the currency of the cesspool, and as a result, it has become commoditized. You can purchase fake engagement just like you can followers. There is a whole micro-economy that lives to generate this type of engagement. And there are huge numbers of people working day and night to try to game the cesspool system. People like me. By simply commenting LB (“Like back”) on the recent posts of insanely popular instagram accounts like Kylie Jenner, other poor souls would take the time to click on my profile and like my photos in hopes that I would return the favor and “Like back” theirs in return. Insane, right? Below is Kylie Jenner’s most recent post on Instagram. Take a look at the comment section, and you’ll see exactly what I’m talking about. So, this was my system. Post a hilarious and outrageous photo, comment hundreds of times on Kylie Jenner’s Instagram account to generate phony ‘likes’, and then do it all over again. My College Cards Instagram content was generating hundreds of likes this way, and the page was coming alive. Generating fake comments was harder. Especially for an Instagram account like College Cards. I could have simply commented “Comment back” or “CB” on Kylie’s posts, but doing this would only get me a bunch of pre-written comments like “So inspirational <3” or “Love THIS” (perhaps you’ve seen these fony comments on some of your friends’ Instagram posts!). I didn’t want these spam comments on my posts. I wanted real comments talking about how freakin’ awesome my card game was. It’s these types of comments that inspires people to take action and purchase the game. So I simply recruited my friends and asked them to comment on my new Instagram account for the game I was creating. I had sent them copies of the game prior, so they were commenting their honest opinions about the game—they just needed a little push from me! The Stage Was Set After a couple weeks worth of work, my Instagram account was done. I had about 12-15 photos in my gallery showcasing hilarious card combinations from the game. Each photo had more than 100 likes and were filled with comments from my friends saying how much fun it was. Pre-Launch At this point, I had spent months preparing for launch day. My launch plan was simple: send as much qualified traffic (University of Wisconsin students) as possible to the College Cards Instagram page. If my thesis was correct, this traffic and these people would check out all of the pictures and posts and I had worked so hard to generate and pump up with fake engagement. They would see how great this game was and potentially buy themselves a copy. To drive this qualified traffic to the Instagram page, I did a couple things. 1. Get UW students to post and tag @College_Cards in their Instagram stories Prior to the day of launch, I reached out to all of my UW friends and connections and explained the game I had created and how I really could use their help to get the word out on the day of launch buy tagging @College_Cards on their Instagram stories. All of my close friends were happy to do this for free. For others I offered discounts and free games in exchange for shoutouts. For everyone who agreed to participate, I sent a number of product pictures/card combinations of the game that showcased it being played. I instructed them to write whatever they wanted about the game and simply tag @College_cards on the day of launch. Using this method, I had between 30-50 Instagram accounts ready to shout out the game on launch day. 2. Aggressively follow as many UW students as possible On the day of launch (as well as days following the launch), I spent hours and hours simply ‘following’ students on Instagram who went to UW Madison. This was extremely time consuming, but for every person I followed, they received a notification showing that “College Cards” just followed them. They then proceeded to check out our instagram account showcasing the game. The Launch The combination of these two things sent a wave of traffic to the Instagram account on the day of launch. My phone completely blew up that day with notifications, alerts, and messages. Just as planned, people were tagging their friends, commenting, liking, and messaging in asking how they could get a copy of the game. The techniques mentioned above drove thousands of page impressions and hundreds of click throughs to the website where the game was for sale. The game was selling fast, and that first day I sold more than $2,400 of College Cards to students who found us through our Instagram account. 45 days following the launch, I had officially sold more than $13,000 of the game almost solely through Instagram. So then what happened? About a month after the launch, the virality of the game started to take on a life of its own. School newspapers were talking about, kids on campus were playing the game with their friends, and those friends were then buying the game and playing with their friends—starting the process all over again. The flywheel was rolling. Unfortunately it all came crashing down once the intellectual property law firm that represents the University caught wind and demanded I shut the whole thing down. I wrote about the entirety of these events in my blog post describing exactly how I manufactured, marketed, and wound up having to shut down the game here: . The Story of College Cards Takeaway College Cards was my first official business venture. I had an absolute blast building it, and more importantly I learned so much doing so. Since then, I have started a number of other businesses like which has allowed me to quit my “9 to 5” and live life on my terms. While building these other companies, I’ve learned even more about the best possible ways to drive amounts of traffic, users, and customers. this tax software company insane I love sharing these real-life growth tactics with as many people as possible. If you enjoyed this article, you should I talk about my first-hand experience with the best possible ways to market and grow your business in today’s competitive environment. I’ll see you in the inbox! sign up for my email list here !

LOCALIZE

localizejs.com

11-50 employees

Since 2015

COMPANY RANKING

LOCALIZE

EVERGREEN INDEX #7004

Representing this company? Click here to claim and customize this page!

Localize WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

LOCALIZE

localizejs.com

11-50 employees

Since 2015

COMPANY RANKING

LOCALIZE

EVERGREEN INDEX #7004

RELATED COMPANIESRANK

STORIES ABOUT LOCALIZE

Representing this company? Click here to claim and customize this page!

Localize WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!