If you build the service in 10 languages right away, you’ll struggle to maintain it. Every interface change means updating translation files across all languages, even though most of your users will likely understand an English interface anyway. But if you’re building for a specific country, build it in that country’s language and don’t add English. Even two languages at the start are worse than one. With a single language, you can keep text directly in the code instead of splitting it into separate translation files.
My blog: orchidfiles.com
codingdave•34m ago
Take the time to extract UI strings from the code, even if only building a single language. It isn't that complex, and will certainly pay itself back if you get any traction at all.
theorchid•32m ago
codingdave•23m ago
That is really just some file organization and some code syntax, not a major architectural difference. And it gets you a long way towards going multi-lingual when you need it, without much effort at all.
theorchid•20m ago