Building for i18n from the start

We decided to build the product with two-language support from day one. This decision added a little work upfront but saved a lot of time later.

The main rule we follow: no strings directly in code. All text goes through keys in localization files. This instills discipline and makes adding a new language a manageable process.

Second point: localization isn't just text translation. Date formats, number formats, text direction — all of this needs to be considered in advance. Adding it after the fact is significantly harder.

Boring discipline that pays off later.