App localization costs are usually hard for developers to quantify, unless they’re working with someone who knows how it works. That’s why at Babble-on we answer every request for localization costs fastâ€”typically within 15 minutes!
But is that fast enough, or even the best way? We’ve noticed that developers are a shy bunch. They want to estimate localization costs but they often don’t want to email or call to find out. That’s why we created a free App Localization Costs Estimator widget right on our website:
This easy localization cost estimation widget makes it possible to calculate costs down to the penny instantly. Try it for yourself by uploading your Strings file, app description, and keywords:Â App Localization Cost Estimator.
How the Localization Costs Estimator Works
It’s simple. Click “Add file” or just drag your files onto the button. The localization cost estimator can count the words and strings in a whole bunch of file formats. Next, choose the languages you are interested in. You’ll see the exact cost for everything, and you can add or subtract languages and files until you reach your budget. Remember, the prices include everything from expert handling of localization formats and encodings (like UTF-16 Localization.strings files), to real-live-human tech support by phone or email. Babble-on isn’t a factory, and that kind of attention means a lot once you get started localizing.
File types the cost estimator can count:
- iOS .strings
- Android .xml
- Windows 8 (Metro) .resw, .resjson, .resx, .rc
- Java/Flex .properties
- Ruby on Rails & YAML .yml
- BlackBerry .rrc
- GNU GetText .po, .pot
- XLIFF .xliff, .xml
- Microsoft Office/Open Office .docx, .xlsx, .pptx, .odt, etc.
- Plain Text .txt
- Qt .ts
- DKLang .dklang, .lng
- XUL .dtd
- Google Chrome Extension .json
- Subtitles .sbv,Â .srt
Which languages should I localize my app into?
The most popular languages are Spanish, French, German, Italian, Portuguese, Japanese, Korean, and Simplified Chinese. Of course it depends on your target and your budget. My suggestion is always to start with one, preferably a language for the country you are already seeing some traction in. For example, if you see downloads outside the US usually come from Japan, then Japanese should be your first pick. Check iTunes Connect or the Google Play store to verify your download stats. If you aren’t sure, stick with the largest markets like Spanish. Contact us for personalized advice.
Read our press release: San Francisco iOS App Localization Service Says No to the Factory Model and Introduces CostÂ Estimation Widget