Handing off UX copy to developers and translation teams can be a mess. Developers might use copy from some old design file. They have to manually copy and paste each string into code (which leads to errors). And translators have no context for the copy they are tasked to translate. With Strings, handing off copy saves time, mitigates errors and adds transparency for localization teams.
You can find our plugin in the Figma community:
To get your designs and copy ready for implementation, we recommend to name the frames and elements in your Figma file so they can be recognized by your developers. Strings uses them to create the string names in code. (But not to worry, your developers can always rename them.)
Open the Strings plugin you installed and select the frames you want to export. Keep in mind you can always re-export the same frame. Strings automatically pulls in the updated version to your project and updates the code based on the latest designs.
In Strings, you can review the project. You can leave notes for your developers and localization team. You can also exclude strings that should not be in the code export (e.g. duplicates or placeholder copy).
We know that most translators do not have access to design files or product documentation. We therefore created a specific view for localization teams. They can see the designs, associated copy next to it and any comments you want to leave them for context.
