Mailspree will be english-only at first because it's the most spoken language around the world and has the best potential to reach the most people. Long-term I am planning to translate into German (I am German), French, Spanish and maybe Russian, depending on the needs of my future customers :)
English/Japanese right now. Bringing Japanese texts to life for language learners with a high command of the English language. In my specific market, Japanese-learners are actually primarily not English-speaking, but I'm going after a specific share first.
Early on will be English only, but I have the feeling that traction will increase if users see the tool in their native language so I am thinking to cover 4-5 general languages after launch.
Languages help quite a lot in improving conversion rates. Especially if your product is consumer-facing for your customers. English & Spanish are somewhat key.
I am more curious about the tools/methods Indies are using to make it happen. Google translate is not quite helpful here. I use a simple custom API, with English as default.
Unfortunately I have no metrics (or customers) but from the very beginning Lakebed has loaded content from language specific content files. I did this because I hope governments can use Lakebed to host their open data and, in Canada specifically, that means it needs to be in French an English.
I'm quite passionate about localization b/c it's an accessiblity issue just like making sites work for screen readers and providing CC on videos.
Mailspree will be english-only at first because it's the most spoken language around the world and has the best potential to reach the most people. Long-term I am planning to translate into German (I am German), French, Spanish and maybe Russian, depending on the needs of my future customers :)
English/Japanese right now. Bringing Japanese texts to life for language learners with a high command of the English language. In my specific market, Japanese-learners are actually primarily not English-speaking, but I'm going after a specific share first.
Early on will be English only, but I have the feeling that traction will increase if users see the tool in their native language so I am thinking to cover 4-5 general languages after launch.
Same!
In English, as always. Yet we're talking to the French market.
I'll probably translate the site into French later.
Languages help quite a lot in improving conversion rates. Especially if your product is consumer-facing for your customers. English & Spanish are somewhat key.
I am more curious about the tools/methods Indies are using to make it happen. Google translate is not quite helpful here. I use a simple custom API, with English as default.
Unfortunately I have no metrics (or customers) but from the very beginning Lakebed has loaded content from language specific content files. I did this because I hope governments can use Lakebed to host their open data and, in Canada specifically, that means it needs to be in French an English.
I'm quite passionate about localization b/c it's an accessiblity issue just like making sites work for screen readers and providing CC on videos.
That’s totally true it’s also an accessibility feature!