Translations Strings

Name: Translations Strings
Rating: 5.0 (1 reviews)

Translations for apps via AI + Human (if needed)

5.0•1 review•

118 followers

Translations for apps via AI + Human (if needed)

5.0•1 review•

118 followers

Visit website

AI-driven i18n - because managing translations is just a pain. - Almost any language, formal and informal. - Version history of each string. - Integrate into your apps via our API. - It's also free (v0.1 - it's ugly, I know)

Free

Launch tags:API•Languages•Artificial Intelligence

Launch Team

Viktor.comAn AI coworker that actually does the work

Promoted

Liffery

Maker

📌

Hey Product Hunt friends! At Liffery, we're just getting ready for our public launch, and in doing so, we're getting the platform translated... but... having gone through the joys of i18n before, coordinating translators and developers is always challenging, and this time I wanted to see if we could optimise the process. With this utility tool for app development teams, we wanted versioning, translation context and an API for DevOps. But we also wanted to speed the whole thing up... a lot... so we mixed in ChatGPT. After a few days of rapid development, the database model is stable, the API is stable, and the access to ChatGPT is rock solid, so we thought... why not just release this on a domain for all to access and see what people think. We have a few ideas for where we would like to take this (starting with getting a UX and graphics designer on board to make it look less 1992), but we would love to hear your thoughts! Happy translating :D John PS: There are not many glossy images for this mini project yet, but the video explains most features.

Report

3yr ago

@john_carmichael congrats on the launch mate 👏🏼

Report

3yr ago

inlang IDE Extension (i18n)

Cool project. But, the approach you are taking (of having an API to fetch translations from) will eventually fall apart. Developers and translators will simultaneously change translations. Technically, you have no possibility of merging changes from developers and translators if you don't have version control with branching support on your database. I explained the technical challenges and solutions in this video https://youtu.be/CZr6A5gwmFs?t=825. TL;DR we are building turning git into a database now and building localization infrastructure. If you want to reduce maintenance effort + have a better i18n experience, you could build translations strings on top of https://github.com/inlang/inlang. See https://inlang.com/documentation....

Report

3yr ago

Liffery

Maker

@samuel_stroschein actually the API does comparison checks as the new data is provided. Updating if needed, creating if new... or ignoring if it is exactly the same. So you can just keep throwing data at it all day long, the same, different... it will just all be handled by the API. I think i mentioned it in the vid but, the translations are also versioned :) There are a few other platforms that do this already but... we just wanted one with ChatGPT thrown into the mix :) In other words.. it will not fall apart as you say.

Report

3yr ago

Liffery

Maker

@samuel_stroschein but that is a good point! I will get the video update thank you! Ref.: managing bigger teams with translation strings. In my experience over the last 15-20 years, devs should not be writing the copy - only add placeholders for the copy-writers. My experience with the majority of no-techy folk is git is not a nice place for them to be. The way we work with Translation Strings, is simple... the devs work in the JSON files as they always have. They work in 1 language (for us English). And so.. all changes for this are managed in git.. just as it always has been. Depending on how your app is setup, you will either have 1 big JSON file, or lots of smaller JSON files that a for areas of the app. The dev works up a feature, the feature is tested and merged into branch develop (aka gitflow). However, before we move to production the translations are checked by the copy writers (this could be finallised before the feature, and give the dev the text to copy and paste in) but for us it is more efficient this way... and now with Translation Strings, automatically translating... we have English to 6 other other languages in the no time! I guess 1 big improvement there would be to have a simple sync tool between the IDE and the API of Translation Strings... but for now, with this POC, the workflow will always be to take the English file from the code, put into Translation Strings, and then pull back out int the app along with all the other translations. Thanks for the idea 💡 great feedback

Report

3yr ago

inlang IDE Extension (i18n)

@john_carmichael Thanks for the detailed response! Re managing larger teams: Absolutely, devs should work in git and translators should have an easy way to manage translations. > I guess 1 big improvement there would be to have a simple sync tool between the IDE and the API of Translation Strings This is the moment you will eventually need version control on your database layer. Syncing state with branches will become a nightmare/impossible (been there done that :D).

Report

3yr ago

Govar – English speaking app

Hey! Congrats with the launch! Great job! How do you think can I use it to create localisations of my app for appstore and google play? Now I'm planning to do it but I afraid translation won't be correct.

Report

3yr ago

Liffery

Maker

@dzianis_yatsenka great question! We also have apps in both... With the app stores, we have found that the biggest pain point is sending out the app with the translations embedded as then a change requires a new app release... not optimum! In Liffery, before we go public live we intend to change how the translations are pulled into the app. Today, webpack bundles the JSON into the app. We will instead change this. We intend to configure the app to be bundled with a JSON file... but then on load also look for updates, when there are updates they will then be written to file within the app and i18n will load the translations from there instead... this will also allow is to play with AB testing. 2 features we will need in Translation Strings is... AB options but also... project-key + lang-code last updated.

Report

3yr ago

Govar – English speaking app

@john_carmichael Thank you for your answer! Good luck!

Report

3yr ago

Sealit

Great tool! 🤩 Happy to find it, no doubts it will be helpful in the upcoming ideas on our roadmap! Big congrats on the launch 🙌✨🥳

Report

3yr ago

Liffery

Maker

@maria_brm Thank you! hope it will help over at Sealit!

Report

3yr ago

Sealit

@janine_nitz No doubts it will 🙏💪✨

Report

3yr ago

Promptly

Given the power of GPT-4, translation using AI just completely makes sense. I think it removes a lot of manual effort. Good luck John1

Report

3yr ago

MegaVote

Congrats John and your team on the Translation Strings launch! As someone who knows the i18n struggles, I appreciate your efforts. It's impressive that you're offering this for free. Looking forward to seeing the future of this project, collected and supported!

Report

3yr ago

Liffery

Maker

@maxtpham to be honest... when I put this one together over the easter weekend, it was really just for my own use in Liffery. Maybe I will have to think about a free and paid access in the future if it gets any traction... probably something like an API consumption model. Free for the small apps, paid for the bigger ones... but would you pay for a tool like this?

Report

3yr ago

Not a developer, but definitely see the advantage. Cool thing.

Report

3yr ago

Liffery

Maker

@pjw yuuppp... it is not 100% accurate unless you put in the content for the harder-to-understand translation strings, but I translated all of "Translation Strings" with "Translation Strings" in a coffee break! A couple of errors but... it's definitely a game changer for us at Liffery!

Report

3yr ago

1 2

5.0

Based on 1 review

Review Translations Strings?

Reviews

Most Informative