It just does not work for a workflow with multiple parallel branches. There are only 2 ways to share translations between branches: TM and duplicates. Both approaches are not great:
-
TM is bound to approvals
-
Duplicates don’t work well when deleting branches
We have like 10-20 branches merged a month and if we don’t delete them regularly, the Crowdin project will just turn into a mess. Imagine 300+ branches in one year, that’s too much even just for people to scroll through.
We can’t block our releases waiting for proofreaders approvals for every feature in every language, because it will affect our go-to-market metric. Instead, we want to release the feature ASAP with AI pre-translated string and then eventually go through approvals asynchronously.
I don’t think you understand how your product is used in a fast-paced environment of 2025’s software engineering. There are not so many companies that can afford the idealistic way of mandatory approval of every string. Manual review requires people intervention and it’s always slow.
Moreover, considering that with latest AI models the quality of pre-translation rises, it should be totally okay to allow adding AI-generated messages to TM. It should not break the current Crowdin’s recommended approach, it just gives freedom to your customers to decide what to think of TM themselves. We are okay to treat TM as just a place to store translations to share them between branches without approval.
Could you please propose alternative ways to achieve sharing of messages between branches, so that branches can be deleted without fear of losing translations, while still leaving them unapproved?
If that isn’t possible, I would greatly appreciate concrete next steps rather than simply hearing “it’s a feature, not a bug.” Could you kindly share this feedback with your product team and ask them to provide further details?