[obviouslygreen]

"Localize your app" is a serious overstatement for what's covered by this article. To actually localize an app, automation is not an option, nor is just getting your keywords and descriptions done.

If your target audience is international but you can reasonably expect them to speak your language but to search in their native tongue, OK, this makes sense. But that's a large target for a small segment.

Localization is a process that involves your translator understanding your product, the terms it uses, the context in which it uses them, and how those terms can be transitioned into their target language. That's a far cry from keywords and descriptions, and it matters in many cases. Those cases never stop at $300.

It's often worth doing (this is totally dependent on your goals, though) but in the case that it's worth doing for you, it's also worth deciding whether you want to actually do it or whether just making sure people find your app is OK or whether you want them to be able to use it in their native language. Huge difference.

[mrborgen]

True enough, if you want to fully localize your app, you'd have to spend much more money and time.

However, I'd definitely not recommend people translating their entire apps without localizing it's metadata first to check your apps potential in various markets.

For a lot of apps, including our music making app, it's meaningful to reach out wide even though the language within the app is english, as it's not a very text based app.

The result will give us a good overview over which languages that has the most potential, which we later on can consider to localize fully for.