AiProductsHunt AiProductsHunt
AiProductsHunt
Translation Strings

Translation Strings

Translations for apps via AI + human (if needed)

Visit Website
Translation Strings
Translation Strings
About Details
Name: Translation Strings
Submited By: Toni Kutch
Release Date 2 years ago
Website Visit Website
Category API Languages GitHub

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)

Enrico Wiza

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

10 months ago

Hillard Halvorson

Congrats 🚀

10 months ago

Michel Heathcote

Congrats on your launch, by the way i like the 1992 style! :) Upvoted!

11 months ago

Rahul Goyette

Congratulation @John Carmichael🚀🎉

11 months ago

Quincy Medhurst

nice one

1 year ago

Makenna Eichmann

Really cool! Will test

1 year ago

Floyd Botsford

That's so cool! great work @janine_nitz

1 year ago

Jackson Fisher

Love that it's free Will definitely be useful for evoke-app.com's API

1 year ago

Marcelo Prohaska

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

1 year ago

Kay Balistreri

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

1 year ago

Wiley Lubowitz

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!

1 year ago

Curt Nienow

Congrats on the launch!

1 year ago

Kenneth Corwin

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.

1 year ago

Scotty Feest

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 <a href="https://youtu.be/CZr6A5gwmFs?t=825" target="_blank" rel="nofollow noopener noreferrer">https://youtu.be/CZr6A5gwmFs?t=825</a>. 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 <a href="https://github.com/inlang/inlang" target="_blank" rel="nofollow noopener noreferrer">https://github.com/inlang/inlang</a>. See <a href="https://inlang.com/documentation/build-on-inlang" target="_blank" rel="nofollow noopener noreferrer">https://inlang.com/documentation...</a>.

1 year ago

Korbin Effertz

Congrats on the launch of your new product.🚀 You've put in a lot of hard work and we know it will pay off😊 👍 Just tried Liffery's translation utility tool and it's a game-changer! Versioning, translation context, and an API for DevOps all in one. Plus, ChatGPT integration makes it lightning-fast. Excited to see where they take it! 🚀 keep it up @john_carmichael and @janine_nitz

1 year ago