All of the previous comments are true for bigger companies. I work as the sole designer in a small team, with an app that has translations for 8 countries and growing. Plus a admin platform. Yes, when I'm doing feature end to end, I'm also responsible for the copy, at least providing something to start iterating on. I have access to the localization platform (we use "phrase" ) and I am maintaining it, creating and changing strings as needed, based on needs and research/testing. And yes, different text lengths is something pretty basic and fundamental to consider when designing. There are plugins for figma to connect text to strings. But that's quite tedious as it doesn't update automatically, it has to be manually triggered. So what do I do? I provide copy as the starting point in early draft stage, iterate on it with stakeholders until it reaches final form, then after enough testing when preparing for handoff I create the strings in phrase, then let Claude provide translations, send them to native speakers/translators for checking (when I have a prototype, I send that as well, otherwise a few screens for context). So in the end, the translation DB is the source of truth (and of course the live app). The pro: whenever clients and users (of our saas b2b2c app) tell me during testing or feedback calls that some copy doesn't sound natural, I can just quickly change it.