Internationalization Is Architecture, Not Translation: A Deep Dive with Jan Amann • 6 min read
Most developers, especially front-end developers, believe they get internationalization because they know how to translate strings.
However, as Jan Amann put it on The Agile Localization Podcast, that belief is exactly the root problem. Internationalization is not translation; it’s product architecture.
It’s how you model language, market variants, currency, locale, routing, content pipelines, testing, layout impact, and performance before you even think about translation keys. That is the mental switch most developers never make and why so many multilingual projects fall apart as soon as you add the third language, the first regional variant, the first new market, or the first SEO requirements.
Jan has been thinking about this for half a decade. He’s the creator of next-intl (the internationalization library used by Ethereum’s website) and author of the i18n course for React/Next.js devs.
And he says that developer misconceptions are the #1 blocker to building apps that actually scale globally.
Listen to the new episode on:
- Apple Podcasts
- Spotify
- YouTube