Localization.One

I’ve been using this product for two gaming communities, so I thought I understood the core workflow.

Then I tested it as a new user.

You could create a project, but you could not import an existing JSON, XML, PO, ARB, or other localization file into it. The options were the API or adding strings one at a time.

That was a pretty embarrassing gap for a localization product.

I added an “Import file” flow to existing projects: upload, detect the format, preview the strings, skip duplicate keys, and import the rest. I then tested the full loop with a second import, AI translation, review, and export.

The lesson for me: dogfooding is useful, but it can hide onboarding problems. When you already know the API and every shortcut, you stop seeing what a new user sees.

What obvious workflow did you only notice was missing after launch?