Localization is one of those features every app needs and nobody wants to think about. You add a library, wire up a JSON file, and move on. Then you upgrade React Native. You turn on the New Architecture. Google Play starts asking about 16 KB page sizes . Your Arabic users report that "2 items" reads wrong. And the language your user picked is gone after the app restarts.

I hit every one of these, so I built react-native-i18n-kit : a fully native, zero-dependency localization toolkit for React Native, written in Kotlin, Swift and strict TypeScript.

npm install react-native-i18n-kit

Enter fullscreen mode

Exit fullscreen mode

Why build another i18n library?

I looked at what was out there and kept finding the same gaps:

JS guessing at native facts. Many libraries read a locale string and work out everything else in JavaScript. But the device already knows its calendar, time zone, decimal separator, 12/24-hour preference and measurement system. Why not ask it?

Built before the New Architecture.…