Because there is no need for something like i18n to be moved to some SaaS it just adds complexity to the whole project and you are probably doing unnecessary Network calls using this service unless you export the JSON from this SaaS and use it in production which is then anyway the same as not using the service, so why should I use this just to look at my strings in a nice designed dashboard and edit them? Who thinks he needs this ok but I think its unnecessary.
First of all, when you are translating your app into multiple languages, the development is full of repetitive tasks. Extracting the keys, modifying the localization files etc. It you are translating to multiple languages, then you would be probably annoyed with those tasks.
The more important part is providing context to translators. When you localizing your app into languages you don't know, then you have no way how to check, that your translators provided accurate translations. Without context, you can be sure, that they will provide inaccurate translations.
The thing is, that it's not just developers who needs to manipulate the strings. It's also translators, who don't understand and sometimes can't even access the code of the app.
Because there is no need for something like i18n to be moved to some SaaS it just adds complexity to the whole project and you are probably doing unnecessary Network calls using this service unless you export the JSON from this SaaS and use it in production which is then anyway the same as not using the service, so why should I use this just to look at my strings in a nice designed dashboard and edit them? Who thinks he needs this ok but I think its unnecessary.
First of all, when you are translating your app into multiple languages, the development is full of repetitive tasks. Extracting the keys, modifying the localization files etc. It you are translating to multiple languages, then you would be probably annoyed with those tasks.
The more important part is providing context to translators. When you localizing your app into languages you don't know, then you have no way how to check, that your translators provided accurate translations. Without context, you can be sure, that they will provide inaccurate translations.
The thing is, that it's not just developers who needs to manipulate the strings. It's also translators, who don't understand and sometimes can't even access the code of the app.
You are right maybe I'm thinking wrong about this, I will check it out and let you know.