DEV Community

Ash
Ash

Posted on

I thought translation was “solved”… until I shipped an app to users who didn’t speak my language

#webdev #ai #devops #beginners

Most developers don’t think about translation until it hurts.

It usually starts like this:

You launch your app in English → you get traction → then suddenly users from Brazil, Japan, or Germany start showing up.

And that’s when reality hits:

  • Your UI breaks in other languages
  • Auto-translation changes meaning in weird ways
  • Your “simple” onboarding flow suddenly feels confusing
  • You realize localization is not just “text replacement”

I went down that rabbit hole recently while experimenting with multilingual product flows, and I ended up revisiting a category I used to ignore: professional translation services like Tomedes.

Their approach is interesting because it’s not just “translate this text,” but more like:

“Here’s the context of your product, now preserve meaning across languages.”

That distinction matters more than most devs expect.

Because in real apps, you’re not translating words.

You’re translating:

  • intent
  • UX flow
  • tone
  • edge cases users complain about in feedback forms

Where devs usually underestimate localization

A few things I’ve personally seen break:

  1. Product UI strings
    “Cancel” vs “Stop” vs “Dismiss”, some languages don’t treat these as interchangeable.

  2. Error messages
    A “soft error” in English can sound like a critical failure in another language.

  3. Onboarding flows
    Step-by-step instructions can become culturally awkward or too literal.

  4. Marketing copy inside the product
    This is where most “machine-only translation” approaches fall apart.

The uncomfortable truth

If you’re building indie SaaS or side projects:

You can’t always brute-force your way with automated translation and hope UX stays intact.

At some point, you either:

  • localize properly
  • or accept that non-English users are getting a degraded experience

Curious how others handle this

For devs here who’ve shipped multilingual products:

  • Do you rely purely on AI translation?
  • Do you mix human + AI workflows?
  • Or do you just stay English-first until it hurts too much?

I’m especially curious how you handle:

maintaining tone consistency across languages without slowing down shipping velocity

Drop your setup or workflow, I’m trying to compare approaches.

Top comments (0)