Take Your App Multilingual (No Rewrite)

"We should support Spanish" is a sentence that strikes fear into engineering teams. Not because translation is conceptually hard, but because retroactively adding language support to an app built entirely in English feels like it requires rearchitecting everything. It doesn't. At least, not all at once. There's a pragmatic middle ground between "English only" and "fully localized in 40 languages." Most teams never find it because the discussion jumps straight from "we need Spanish" to "okay, let's implement i18n across the entire codebase." That's a months-long project. There are faster ways to start. Start With the Content, Not the UI The typical internationalization approach starts with the UI framework. Extract every string into a translation file. Set up locale routing. Configure date and number formatting. This is the right end state, but it's the wrong starting point for most teams. Start with user-facing content instead. The parts of your application where language actually matt