@sebdziecielski True. Works well in my case since itโs a low stakes consumer product. about 40% of my users are non English speakers and I rarely get mistranslation reports and even when I do it helps improve the process
If youโre building a consumer app, you don't need a localization platform.
We built ours in-house with GitHub Actions, translation APIs, and an LLM as a native speaker.
About 40% of our users use the app in another language.
Our setup is under $30/month. Lokalise, or something similar, is around $400/month.
This may not fly in healthcare or legal, but for most consumer apps, localization feels like a solved problem.
our app is native swift with a lot of location + background audio stuff
thinking about building android with react native and then migrating ios over at some point
anyone done this with a location-heavy app before?
@MetaReflexive The scene seemed appropriate because it represented the time passing and the battles fought in the 4 years that MJ and Ned were in college