Forthwith
Translate your app with AI—without breaking placeholders, pl
brew install Forthwith-LLC/forthwith/forthwithDetails
- Follow on
- Categories
- Use Cases
- Target Audience
- Pricing
- Subscription from $49
- Platforms
Discovery signals
How AI and people discover Forthwith on PeerPush
- ChatGPT
- Perplexity
- Claude
- +4 other AI crawlers
Reads by these AI engines
Crawlers behind these engines read this listing on PeerPush.About Forthwith
Forthwith is an AI-powered localization tool built for developers who want to ship their apps in more languages without adding a painful or expensive translation workflow. Run `forthwith translate` from your project, and Forthwith finds new or changed strings, translates them, and writes the results back into your existing localization files. Unlike asking an LLM to translate your apps strings, Forthwith also validates the things that can easily break during translation—placeholders, interpolation variables, plural forms, markup, escaping, and file syntax—before writing changes. Forthwith supports iOS, Android, Flutter, React, React Native, Phoenix, and go-i18n, so localization can stay where it belongs: in your normal development workflow.
Product Video
Watch a video demo of Forthwith.
Screenshots
Product Updates (5)
Word packs are live!
My design partner, Roman at LinkFlick.com, made a good point: some people don’t want another subscription. They just want to pay upfront and top up when they run out. So I added word packs to Forthwith! You can now buy 100,000, 300,000, or 1 million words that never expire. Translate at your own pace. When you need more words, buy another pack—or choose pay-as-you-go Flex or a monthly subscription if that suits you better.
Comments (0)
No comments yet. Be the first to share your thoughts!
GitHub PR automation
Over the past week, I’ve added GitHub PR automation to Forthwith. You can now run `forthwith check` and `forthwith translate` through GitHub Actions, bringing localization checks and translation into your PR workflow. I also introduced project-scoped service accounts, so automated workflows can use credentials tied to the project they need to access. Less manual work, with localization built into the development process. forthwith.dev
Comments (0)
No comments yet. Be the first to share your thoughts!
Cldr.Gettext.Plural support added for Phoenix apps
Forthwith now supports Phoenix apps using Cldr.Gettext.Plural 🎉 Forthwith automatically detects CLDR-backed Gettext configuration and correctly handles each locale’s plural categories and .po slot mapping—including Russian’s one, few, many, and other forms. Safer, more accurate Phoenix localization with no extra configuration required.
Comments (0)
No comments yet. Be the first to share your thoughts!
New blog article posted
I just posted a new article on the Forthwith blog. It's super nerdy, but I think it will be a very interesting read for anyone who does Elixir/Phoenix development, or who uses CLDR. Enjoy! https://forthwith.dev/blog/cldr-plural-rules-vs-gettext
Comments (0)
No comments yet. Be the first to share your thoughts!
Prompt shortening for more usage!
Today I strategically shortened the translation prompts I use in three ways: - Only send relevant examples to help the model (I was sending all of the examples in all cases) - Remove duplicate instructions (including some output instructions that were already covered by previous instructions - Send a shorter retry prompt if the model makes mistakes with the initial prompt, instead of sending the entire prompt + the retry prompt I did this, because I want Forthwith users to get the best bang for their buck, and prompt words count towards the total billable words. This will enable you to get more translations with the same subscription. Enjoy!
Comments (0)
No comments yet. Be the first to share your thoughts!
Reviews (3)
Average 5.0 out of 5
Based on 3 reviews
Comments (3)
Great idea!
Nice! I've really been missing something like this
I’m excited to finally share Forthwith! I built it to make app localization feel like part of the normal development workflow instead of a separate translation process.