Alternatives
Products that do what A component-first approach to internationalization does
- 1MY
2019 · github.com
- 2AA
2020 · github.com
- 3BA
2020 · librelingo.app
- 4AS
2017 · play.google.com
- 5SA
2016 · grvcoelho.github.io
- 6AM
2018 · geogee.me
- 7PI
2015 · thesage21.github.io
- 8YB
2015 · github.com
- 9SA
2018 · github.com
- 10IF
2025 · intlayer.org
- 11AS
I built this because I was frustrated with how messy translation files get as projects scale. Most i18n solutions force you to manage big JSON dictionaries, spread across multiple files, and then manually wire everything into your UI. It quickly becomes hard to keep things organized, especially in component-heavy apps. This approach is component-first i18n: translations live close to the UI they belong to. That makes it easier to keep things organized, avoid duplication, and scale without the usual chaos of string management. It’s lightweight, works with React/Next.js, and is designed…
2025 · github.com
- 12
- 13FN
2017 · itunes.apple.com
- 14LT
2015 · longesttranslation.com
- 15ST
2014 · blog.unbabel.com
- 16ID
2014 · devjargon.org
- 17IA
2025 · github.com
- 18BB
2017 · smallworld.press
- 19BA
2015 · github.com
- 20PE
2017 · pollly.orson.io
- 21LI
2015 · lost-in-translations.amanjeev.com
- 22DA
2024 · github.com
- 23HD
2015 · amsdec.com
- 24I2
2021 · imba.io
Ranked by how close each launch is in meaning, then by votes. Refine with a description →