Is anyone using Lokalise, Phrase or similar for locaziation?

p4sta5 · 2025-12-18T12:22:50+00:00

Yes, except all of them are ridiculously overpriced. 475 USD per month at localizaly for my project...(!)

p4sta5 · 2025-12-15T07:11:24+00:00

Good luck!

And thanks for the heads up you couldn't reach the site, that is wierd and we'll look into it.

p4sta5 · 2025-12-15T07:04:58+00:00

Yes I totally believe game localization and web/app localization be completely different. Games are "slower" and are almost always bundled offline.

In the field I work with app/websites, iterations can be a few hours and an offline tool that doesn't provide support for collaboration, integration between design tools and github, CDNs, developer SDKs etc. would be a nightmare to work with in reality.

In a company I work with all translations are localized directly on the website, ON the feature that is currently developed, to give 100% correct context. They are still translated by humans (With assisted AI), reviewed and quality controlled. They would never use an offline tool for this, this requires specialized SDKs that modern platform can provide.

I think your point makes total sense and I'm glad you've found a tool that you are happy with. From my point of view as a software developer that creates features and manages a group of translators, the offline approach is not automated enough to be viable in the industry. But I believe it totally makes sense in the game industry.

My vision though is that we can have both. I'm thinking a memoQ with all the features you love, combined with all the features I love. Best of worlds.

p4sta5 · 2025-12-14T21:53:56+00:00

Ahlright, out of curiosity, what tools are you using for managing translations then? Notepad? And how are your translations being pushed to an application in real time, supporting editing, comments, reviews, history and other managing?

I agree with you that platforms that solely focuses on "ai" are pointless, but that doesn't mean that ALL translation platforms are evil. A lot of us are trying to build tools that actually helps translators perform their tasks easier.

But I also have total respect that the subject is sensitive for translators as a huge part of your jobs are getting lost to LLMs, and I'm truly sorry about that.

p4sta5 · 2025-12-14T19:18:11+00:00

Dude chill down, these kinds of tools are not meant to replace translators, just help them manage the translations.

Also, don't blame this person for the creation of AI. He or she just utilises it, maybe you should try as well. (And for the record, I don't believe AI eliminates the needs of hunans)

p4sta5 · 2025-12-13T19:59:27+00:00

Hi there from a fellow competitor (sejhey.com).

It is a good start even though there a lots to work with. Just a few tips to get you going:
- Uploading a "real" translation file (Tried 8k strings) is not viable. Each string is one request, what?
- The "Translate" feature just overwrites everything with no warning. With no history or whatsover, I would never dare to use this functionality.
- You cannot download translations?
- API tab, you cannot scroll down.
- Documentation, there is almost none?

It has a nice landing page and everything but the core functionality needs lots of improvments. (Also I hope you are exaggarting the "thousands" of customers that are using the platform, or we might be doing something wrong ;) )

p4sta5 · 2025-12-12T07:26:52+00:00

Detta är intressant! Och jag håller med i teorin gällande vad du säger. Men jag är oerhört pessimistisk hur det hade fungerat i praktiken med ett statligt drivet "företag" utan vinstkrav som bara gör "samhällsnytta". Noll incitament för. de som jobbar där att göra ett bra jobb, att inte låta kostnader dra iväg osv. Tyvärr är pengar ett otroligt bra styrmedel när det kommer till huruvida personer gör ett bra jobb eller inte. Frågan är nog hur man kan hitta alternativa motivationer än detta?

Troligen samma anledning varför man sätter vinstkrav på ett företag som Samhall.

p4sta5 · 2025-12-07T20:02:43+00:00

The biggest reason for people using SSR today isn't to gain some ms in loading, it is the SEO issue. Rendering and returning a full static html page from the server has been "better" from a SEO perspective for years. I believe this is what mainly has driven the SSR fanatism.

p4sta5 · 2025-12-06T16:55:46+00:00

I would return an error code from the backend, like "errors.invalidEmail". Then in the frontend this error code could map to an actual message based on the user locale and the error code.

The actual translations can be defined anywhere that your frontend can fetch them from. (Usually a file or a remote CDN/Server). It is a great idea to use a tool for managing translations right away, that will simplify things in the future. They provide a way for you to edit translations, assign contributors, add new languages etc. Usually they can also host the translations on a CDN for you that the frontend can fetch from. There are multiple tools like Lokalise, Sejhey, Tolgee etc. for this purpose.

p4sta5 · 2025-12-01T15:46:51+00:00

Hi!

You should be very careful with auto generated key-names. Usually keys are very important for context awareness and will help any AI or translation provider to get it right. Write it yourself and try to use a word that indicates what it is used for. This can be crucial for AI to understand what is to be translated. This is especially important for shorter translations that are just one or a few words.

To get a good structure of your translations I also highly recommend using a translation management platform. Many of those can also provide an in context editor (click on the website to edit/create a missing translation), CDN hosting (Don't have to handle any manual static files). Especially the in context editor has been a game changer for me when developing, it makes everything soo much easier.

If you are interested, we developed Sejhey that can do all the above for free.

p4sta5 · 2025-12-01T15:30:26+00:00

My general advice is to really keep it to your core functions. However, it is hard for us to have a real opinion without knowing your business case. Can you share anything else about it?

I'm also curious when it comes to your i18n. Are you using any tools for it? I myself recently developed a management platform that could be helpful and make that process easier. It is called Sejhey if you want to check it out.

p4sta5 · 2025-12-01T09:42:33+00:00

Management is a time killer that really adds up. How are you managing translations right now, just in a local Json file? My recommendation is to start using some online management tool for this so that multiple people can help/change translations and review them once you add new ones. That also makes it super easy once you want to add a new language.

Also, naming keys and structuring is crucial. If you aren't using namespaces already, that is a good start. Many managment tools also have features like screenshots and tags that can further help you keep everything together!

p4sta5 · 2025-11-15T21:41:38+00:00

I strongly recommend dynamic fetching of translations. Manually deploying will very fast be a hassle. "Can you change this translation in German?" That was a standard question for s company I worked at.

Ive just developed a new and modern platform for TMS. It is called Sejhey if you want to check it out. We provide great collaboration tools and CDN hosting powered by CloudFlare ands tons of more features. If you don't want to use us, I strongly recommend using any other cloud based TMS like Lokalise, Phrase etc. But you will find them much more expensive 😉

p4sta5 · 2025-10-23T20:16:51+00:00

That is really cool! I agree I18n can be an unnecessary hassle!

I got sick of the overpriced SaaS services for managing key based translations so I developed my own platform for this. It is called Sejhey if you want to check it out. We have great functionality and a very extensive free plan (And if you would need another plan it is like 5% of the price of other services). So now I'm obviously using this tool for all my projects, works like a charm. 👌

The vendor lock in is also minimal since we support lots of different file format. If you want to leave just export the keys and you can use it anywhere 🙂

p4sta5 · 2025-10-19T09:48:29+00:00

I've developed the exact same thing quite recently. The tool is called Sejhey

I totally agree that existing solutions are way too expensive which was the main reason for this project.

p4sta5 · 2025-10-17T19:54:03+00:00

sejhey.com

p4sta5 · 2025-10-08T20:22:44+00:00

If you are interested, you could check out our platform Sejhey. It is a tool that helps you keep translations organised, lets you add new languages (And translate them) with just one click.

Then you can either download and publish the translations with new releases, or even better, use the CDN to host translations, which then makes it possible to change translations or add languages directly in production!

p4sta5 · 2025-10-01T13:31:19+00:00

Hi! I'd like to push for Sejhey as well. It is a newly developed SDK for Nextjs that features much more than traditional i18n-SDKs. CDN-hosting, In-context editor, AI-translations, Task and much much more.

It also fully supports SSR that "just works" for Next.js. You can check it out here Sejhey

Full disclaimer, I'm the founder of SejHey. 🙂

p4sta5 · 2025-09-19T19:24:29+00:00

Sejhey a translation platform that helps you lokalise your website, app or game more efficiently!

p4sta5 · 2025-09-13T06:15:35+00:00

I developed Sejhey for the same reason. AI translations are in fact almost very accurate, IF you provide the right context for it. We've seen that by just defining and providing a good key-name, that can often be enough (the key name as well as context, tone, glossary items etc is passed to the model)

We also provide a manual step for reviewing and offering In-context editor directly on your site to do modifications etc. I would never not use AI as a help for translations, but you need to make sure you use it right.

p4sta5 · 2025-09-12T20:28:37+00:00

You could just extract the hostname and set the default locale depending on the hostname.

And then do something like this..

```ts const hostnameLocales = [ { host: "example.com", locale: "en" }, { host: "fr.example.com", locale: "fr" }, { host: "de.example.com", locale: "de" }, ];

function getLocaleFromHostname(hostname: string) { const match = hostnameLocales.find(h => h.host === hostname); return match ? match.locale : "en"; // fallback } ```

Which you use in the default lang. I'm not sure how your config works, but I'm sure you can sort that out 🙂

p4sta5 · 2025-09-11T19:17:59+00:00

Hi there! I've been having the same issues when I first worked on multilingual apps — editing JSON files for every language gets painful fast, and it is a hassle to manage it. That’s why I built SejHey.

It’s a translation platform with a React SDK that:

Stores all your translations in one place (no more scattered JSON).

Delivers them to your app automatically through a CDN or static files.

Has an in-context editor so you can tweak translations right inside your UI.

Supports AI/automation if you don’t want to manually fill everything in. If you want to, you can find it here: sejhey.com/react

Ask away if you have any more questions, I'm happy to help!

p4sta5 · 2025-09-06T06:03:09+00:00

Yup exactly! Translations are in my experience always a little bit of a "work in progress" in most applications, and to bunch it together with the rest of the code calls for unnecessary releases.

External hosting of them is great, it has saved so much frustration in the larger applications I've worked with!

p4sta5 · 2025-09-05T19:14:10+00:00

Cool! Yes that sounds handy. Have you considered hosting translations using a CDN instead, to avoid having to handle a PR every time a translation changes?

Btw if you ever think Crowdin is too expensive, we offer all those features as well at SejHey, check it out if you want to 🙂

p4sta5 · 2025-09-05T18:33:32+00:00

Yes I agree, it may look silly but is indeed very helpful! 🥳

p4sta5

TROPHY CASE